compile-knowledge SKILL.md skillA
compile-knowledge from 5dive-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 5dive-ai/skills/compile-knowledge@git:20261023.a3e54d5Pins git:20261023.a3e54d5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 5dive-ai/skills
- Path
compile-knowledge/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261023.a3e54d5, committed Oct 23, 2026
- First version recorded
- Jul 5, 2026
- Size
- 7,401 bytes
- Repository stars
- 2
- License
- MIT
Compile durable, judgement-shaped knowledge into interlinked markdown — atomic files, [[wiki-links]], a maintained index. Use when persistence is asked for explicitly ("save this", "write it to the wiki") or when the work produced a decision record, a cause, or a gap analysis; ordinary factual answers and routine task results are not a trigger.
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
# compile-knowledge ## When this fires Two triggers, and only these: 1. **An explicit persistence ask** — "save this", "write this to the wiki", "update the wiki/memory", "log this finding", "structure this knowledge", "follow the karpathy method". 2. **Durable judgement-shaped output** — a decision record, the CAUSE behind a finding, a gap analysis, a non-obvious fact that cost real work to learn and would cost it again. It does **not** fire on ordinary analytical work. Answering a factual question, summarising a file, explaining code, or reporting a routine task result produces nothing durable to compile. If the only thing you could write down is a restatement of what the repository or the transcript already says, skip it. Durable knowledge is worth keeping as many small, interlinked markdown files, compiled over time and surfaced through an index — not as one giant doc, a chat log, or a one-off file that rots. This skill makes compiling consistent so your agent gets smarter over time instead of relearning the same things. ## Where it goes — pick the right store - **Agent memory** (default, always available): your `.claude/.../memory/` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dwwpde6rrwahckhw/557c61dafd973d3c8a910e2336faa4690425d976124e01ad58152d31b6d974a2.json
Then /plugin install compile-knowledge@markdownregistry-dwwpde6rrwahckhw in Claude Code. It installs git:20261023.a3e54d5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add 5dive-ai/skills/compile-knowledge@sha256:557c61dafd973d3cThe line at the top of this page pins the label git:20261023.a3e54d5, 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_dwwpde6rrwahckhw)
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 5dive-ai/skills/compile-knowledge 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 compile-knowledge from somewhere else? Ask it: where did my compile-knowledge 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 Jul 5, 2026 and Oct 23, 2026, about one every 28 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261023.a3e54d5 latest | 2026-10-23 | a3e54d5 | 7,401 B | A | view · diff |
| git:20260913.5fdc879 | 2026-09-13 | 5fdc879 | 7,174 B | A | view · diff |
| git:20260820.5c1a075 | 2026-08-20 | 5c1a075 | 6,531 B | A | view · diff |
| git:20260727.70f6f98 | 2026-07-27 | 70f6f98 | 5,332 B | A | view · diff |
| git:20260705.d488e69 | 2026-07-05 | d488e69 | 5,212 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/compile-knowledge/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 (7401 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
5dive-ai/skills · 2 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dwwpde6rrwahckhw GET https://markdownregistry.com/api/v1/resolve?ref=5dive-ai/skills/compile-knowledge GET https://markdownregistry.com/api/v1/blob/557c61dafd973d3c8a910e2336faa4690425d976124e01ad58152d31b6d974a2
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.