Menu
Audit the karpathy-style wiki for decay — orphans, dead links, contradictions, staleness. Use for an on-demand health check of the vault.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive a set of issues or a spec to done as an orchestrator: scout context, delegate each unit's implementation to a subagent, review, and commit per unit.
Converge a repo's convention docs to this workflow's — the counterpart to `setup-matt-pocock-skills`. Docs only; run once per repo after the skills are installed.
Review documentation for document discipline — docstrings, comments, and prose (markdown, ADRs, README) — in a subagent. Use when the user wants to review the docs of a change (a diff), or to audit the docs of named files or the whole repo out of band. Separate from code review, so it runs on its own.
Fold new material — inbox captures and named raw sources — into the karpathy-style wiki as atomic, cross-linked pages. Use when draining the inbox or adding a source.
Consult the karpathy-style wiki for knowledge it has already curated — read-only. Reach for it mid-task when you need a concept, convention, tool reference, or past decision the wiki would hold; prefer it over re-deriving. Not for general knowledge, live code state, or facts read straight from the repo.
Present the open issues in dependency order and reason about what to implement next — which are ready, which are blocked, which are underspecified. Use when the user or an orchestrator asks what to work on next, what's blocked, or wants the dependency-ordered backlog before picking work.
| name | wiki-lint |
| description | Audit the karpathy-style wiki for decay — orphans, dead links, contradictions, staleness. Use for an on-demand health check of the vault. |
The entropy defence. Surface what's rotting and propose fixes; apply only the safe ones yourself, flag the rest.
Load the rules first: vault_read "_schema.md" — the closed page-type set, the controlled tag
vocabulary, provenance. Every vault touch goes through the obsidian MCP server (its vault_* /
search_* tools), which reaches the live vault by paths relative to its root — never a filesystem
path. The README covers connecting it.
search_query over the graphFast, exact graph checks no prose linter can do. search_query runs JsonLogic over each note's
NoteJson — links is its resolved outlinks, backlinks its resolved inlinks, and an empty array is
falsy in JsonLogic:
{"and": [{"!": {"var": "backlinks"}}, {"!=": [{"var": "frontmatter.type"}, "map"]}]}.{"!": {"var": "links"}}.[[targets]] resolving to no page (the schema's coverage gaps — pages worth
writing). links lists resolved targets only, so no single query finds these: vault_read each
page, pull its [[…]] refs, and flag any with no matching resolved links entry.(Dead URLs, broken file refs, and markdown style are handled separately at commit time by the repo's pre-commit hooks — no MCP call needed for those.)
status: stale, or updated old on a fast-moving topic. Flag for review.^[inferred] / ^[ambiguous] is
speculation-heavy. Flag it.type outside the closed set, or tags outside the vocabulary. Fix tags
to the nearest existing term; flag type violations.Every page accounted for against each check above, findings as a list. Apply only unambiguous fixes autonomously (e.g. a tag normalised to an existing term); everything destructive stays gated.