memory-systems SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
memory-systems from muratcankoylan/agent-skills-for-context-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add muratcankoylan/agent-skills-for-context-engineering/memory-systems@git:20260629.8fc51c7Pins git:20260629.8fc51c7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- muratcankoylan/agent-skills-for-context-engineering
- Path
skills/memory-systems/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260629.8fc51c7, committed Jun 29, 2026
- First version recorded
- Mar 18, 2026
- Size
- 16,554 bytes
- Repository stars
- 18,377
- License
- MIT
This skill should be used for persistent semantic memory in agent systems: cross-session knowledge retention, entity tracking, temporal validity, graph or vector retrieval, memory consolidation, and memory benchmark selection. Route file-backed scratchpads to filesystem-context, handoff summaries to context-compression, and token-efficiency tactics to context-optimization.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Memory System Design Memory provides the persistence layer that allows agents to maintain continuity across sessions and reason over accumulated knowledge. Simple agents rely entirely on context for memory, losing all state when sessions end. Sophisticated agents implement layered memory architectures that balance immediate context needs with long-term knowledge retention. The evolution from vector stores to knowledge graphs to temporal knowledge graphs represents increasing investment in structured memory for improved retrieval and reasoning. ## When to Activate Activate this skill when: - Building agents that must persist knowledge across sessions - Choosing between memory frameworks (Mem0, Zep/Graphiti, Letta, LangMem, Cognee) - Needing to maintain entity consistency across conversations - Implementing reasoning over accumulated knowledge - Designing memory architectures that scale in production - Evaluating memory systems against benchmarks (LoCoMo, LongMemEval, DMR) - Building dynamic memory with automatic entity/relationship extraction and self-improving memory (Cognee) Do not activate this skill for adjacent work owned by other skills: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4sfce4pwqqyhvcx3/9e2b38ffe9474ba19c93b3d75c80e683705d82e8a4b59af16d603d133bab8d2f.json
Then /plugin install memory-systems@markdownregistry-4sfce4pwqqyhvcx3 in Claude Code. It installs git:20260629.8fc51c7, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add muratcankoylan/agent-skills-for-context-engineering/memory-systems@sha256:9e2b38ffe9474ba1The line at the top of this page pins the label git:20260629.8fc51c7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4sfce4pwqqyhvcx3)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in muratcankoylan/agent-skills-for-context-engineering/memory-systems since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of memory-systems from somewhere else? Ask it: where did my memory-systems come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Mar 18, 2026 and Jun 29, 2026, about one every 26 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260629.8fc51c7 latest | 2026-06-29 | 8fc51c7 | 16,554 B | A | view · diff |
| git:20260629.9749e5c | 2026-06-29 | 9749e5c | 16,554 B | A | view · diff |
| git:20260519.cbc2c97 | 2026-05-19 | cbc2c97 | 16,564 B | A | view · diff |
| git:20260515.0d7595d | 2026-05-15 | 0d7595d | 15,631 B | A | view · diff |
| git:20260318.9cd3073 | 2026-03-18 | 9cd3073 | 15,834 B | A | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds the newest version.
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/memory-systems/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16554 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
muratcankoylan/agent-skills-for-context-engineering · 18,377 stars · license MIT · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4sfce4pwqqyhvcx3 GET https://markdownregistry.com/api/v1/resolve?ref=muratcankoylan/agent-skills-for-context-engineering/memory-systems GET https://markdownregistry.com/api/v1/blob/9e2b38ffe9474ba19c93b3d75c80e683705d82e8a4b59af16d603d133bab8d2f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from muratcankoylan/agent-skills-for-context-engineering
Every file in muratcankoylan/agent-skills-for-context-engineering