vault-curate SKILL.md skillA
vault-curate from jayantak/vaultmem is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jayantak/vaultmem/vault-curate@git:20260801.7078e87Pins git:20260801.7078e87 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jayantak/vaultmem
- Path
skills/vault-curate/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260801.7078e87, committed Aug 1, 2026
- First version recorded
- Jul 24, 2026
- Size
- 8,641 bytes
- Repository stars
- 3
- License
- MIT
"What should I write next?" and "is the vault rotting?" — vault health and gap finding. Trigger on what to document next, where notes are thin, vault cleanup / audit / "groom my memory", a recall that came up empty or hit `DANGLING`, or a Session/Project note that looks structurally wrong.
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
<!-- CANONICAL SOURCE: this repo (jayantak/vaultmem). The dotfiles copy under agents-source/skills/ is synced FROM here — edit this file, not that one. --> # vault-curate — what to write next, and what is rotting `vault-capture` answers "record this." This skill answers the two questions capture can't: **where is this vault thin, and what is decaying?** Nothing else in the system owns them. Run it at a stopping point, when the user asks what to document next, or when a recall attempt came up empty on a topic that should have been written down. Vault routing is the same as everywhere: `vaultmem vaults` for the registry, `vaultmem which` for the vault that routes here. Most commands below take `-v <vault>` to scope to one. ## The gap surfaces — what should I write next? - **`vaultmem dangling --by-target`** — every broken `[[link]]` in the vault, aggregated by missing target and ranked by inbound count. **This is the most-wanted list**: a target three notes point at is one the vault has already decided it needs. Write those first. Fixing a `--by-target` entry usually beats a new note from nowhere — it completes something already half-written. …
Read the whole file at its exact version.
How to install
mdr add jayantak/vaultmem/vault-curate@sha256:f5a8e64c941ed619The line at the top of this page pins the label git:20260801.7078e87, 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_nlsafx5qsgg3glqj)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 24, 2026 and Aug 1, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260801.7078e87 latest | 2026-08-01 | 7078e87 | 8,641 B | A | view · diff |
| git:20260727.6063466 | 2026-07-27 | 6063466 | 7,666 B | A | view · diff |
| git:20260724.ef729e3 | 2026-07-24 | ef729e3 | 8,313 B | A | view |
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 (8641 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
jayantak/vaultmem · 3 stars · license MIT · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nlsafx5qsgg3glqj GET https://markdownregistry.com/api/v1/resolve?ref=jayantak/vaultmem/vault-curate GET https://markdownregistry.com/api/v1/blob/f5a8e64c941ed61999bb006ebbffa9eb855499653460449a13933b1070291958
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.