Add agent-memory-discipline skill and agent-memory plugin - #2681
Open
OlyaTi wants to merge 1 commit into
Open
Conversation
Contributor
🔒 PR Risk Scan ResultsScanned 4 changed file(s).
✅ No matching risk patterns were detected in changed files.
|
Contributor
🔍 Vally Lint Results✅ All checks passed
Summary
Full linter output |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds one skill and one plugin that bundles it.
The problem it addresses
Connecting a memory tool does not make an agent use it. The MCP tools register, the session runs, and nothing is recalled or saved. Users then conclude that agent memory does not work, when what is missing is the standing instruction telling the model when to reach for it.
This is not a case of telling Copilot to do something frontier models already do well. A model cannot persist anything across sessions on its own; that requires an external surface, and using that surface consistently is a behaviour that has to be specified.
What is in it
skills/agent-memory-discipline/SKILL.mdcovers:plugins/agent-memory/bundles that skill with a README.Deliberately backend-neutral
The skill ships no backend and requires no particular vendor. The rules read the same whether memory is a
memory/folder in the repository, a local MCP server, or a hosted one, and nothing in it fails without a specific service. It also draws the line against.github/copilot-instructions.md: instructions carry curated project rules and are read every session, memory carries what accumulates during work and has to be asked for.Disclosure: I work on Mnemoverse, a hosted memory service, named once in the footer as one implementation among three. Written this way on purpose, because a skill that only works if you buy something does not belong in this repository.
Checks run locally
node eng/validate-skills.mjspasses (caught an unquoted YAML colon in my first draft, fixed)node eng/validate-plugins.mjspasses, all 94 plugins and the external catalognode eng/update-readme.mjsandnode eng/generate-marketplace.mjsrun, generated files included in the diffpackage.jsonorplugins/external.json