memory-discipline SKILL.md skillA
memory-discipline from personalclaw/personalclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add personalclaw/personalclaw/memory-discipline@git:20261114.9abeea6Pins git:20261114.9abeea6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- personalclaw/personalclaw
- Path
src/personalclaw/skills/bundled/memory-discipline/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261114.9abeea6, committed Nov 14, 2026
- First version recorded
- Jul 19, 2026
- Size
- 4,343 bytes
- Repository stars
- 10
- License
- MIT
When and how to persist durable memory — save genuine user preferences, facts, and corrections; NEVER persist transient environment failures (a failed command, a flaky network call, a one-off tool error) as lessons; recall before re-asking.
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 Discipline PersonalClaw is **persistent and self-learning** — across sessions it remembers what the user prefers, durable facts about them and their work, and corrections they've made. That value collapses if memory fills with noise. The discipline is simple: **persist what's durable, recall before re-asking, and never store transient failures as lessons.** Tools: `memory_remember` (save), `memory_recall` / `memory_list` (retrieve), `memory_forget` (remove), and `chat_search` (what was said in an earlier chat). ## What IS worth remembering Persist something only when it will still be true and useful **next week, in a different session**. Three durable kinds: - **Preference** — a standing choice about how the user wants things done. *"Prefers pytest over unittest." "Wants concise answers, no preamble." "Uses tabs, not spaces, in this repo."* - **Fact** — durable truth about the user, their environment, or their projects. *"The prod database is `orders-prod` in us-east-1." "Their team's CI is GitHub Actions." "Deploys go out Tuesdays."* - **Correction** — the user fixed something you got wrong; capture the corrected rule so you don't repeat the mistake. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2a4e7tn3x3nernjh/cac83c44debe000868d07f5b50d1e130bd5264048a4100ee0fc1eb78c1aa27d2.json
Then /plugin install memory-discipline@markdownregistry-2a4e7tn3x3nernjh in Claude Code. It installs git:20261114.9abeea6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add personalclaw/personalclaw/memory-discipline@sha256:cac83c44debe0008The line at the top of this page pins the label git:20261114.9abeea6, 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_2a4e7tn3x3nernjh)
2 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 personalclaw/personalclaw/memory-discipline 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-discipline from somewhere else? Ask it: where did my memory-discipline 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 3 versions of this file, between Jul 19, 2026 and Nov 14, 2026, about one every 59 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.9abeea6 latest | 2026-11-14 | 9abeea6 | 4,343 B | A | view · diff |
| git:20261003.32f9320 | 2026-10-03 | 32f9320 | 4,409 B | A | view · diff |
| git:20260719.6892f8c | 2026-07-19 | 6892f8c | 4,288 B | A | view |
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-discipline/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 (4343 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
personalclaw/personalclaw · 10 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2a4e7tn3x3nernjh GET https://markdownregistry.com/api/v1/resolve?ref=personalclaw/personalclaw/memory-discipline GET https://markdownregistry.com/api/v1/blob/cac83c44debe000868d07f5b50d1e130bd5264048a4100ee0fc1eb78c1aa27d2
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.