القائمة
Park an idea, note, or link into the wiki's inbox for later ingest. Use when you or an agent wants to bank a durable thought or source mid-task without stopping to file it.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | wiki-capture |
| description | Park an idea, note, or link into the wiki's inbox for later ingest. Use when you or an agent wants to bank a durable thought or source mid-task without stopping to file it. |
Drop one raw thought into the wiki's inbox/ and move on — capture, not filing.
Load the rules first: vault_read "_schema.md" — it owns the inbox lifecycle and autonomy. Every
vault touch goes through the obsidian MCP server (its vault_* / search_* / command_*
tools), which reaches the live vault by paths relative to its root — never a filesystem path. The
README covers connecting it.
Write one file per capture with vault_write "inbox/<kebab-slug>.md" — light frontmatter plus the
raw content, enough for ingest to work later without you:
captured: today's datekind: idea | note | link | sourcelink: the URL, if anyAppend-only and autonomous. Do not touch sources/ or the synthesized wiki, do not search for
duplicates, do not synthesize — that is wiki-ingest's job. Done when the thought is one file in
inbox/ and nothing else changed.
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.
Audit the karpathy-style wiki for decay — orphans, dead links, contradictions, staleness. Use for an on-demand health check of the vault.
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.