vault-recall
Answer the user's conceptual or technical question using their Obsidian vault as well as general knowledge. Use when the user asks a question (not a task) whose topic appears in the vault MOC digest from session start. Not for task instructions, not mid-task, and not for writing to the vault (that is to-vault).
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- vault-recall
- description
- Answer the user's conceptual or technical question using their Obsidian vault as well as general knowledge. Use when the user asks a question (not a task) whose topic appears in the vault MOC digest from session start. Not for task instructions, not mid-task, and not for writing to the vault (that is to-vault).
02 资源文件 1
- 参考文档evals/evals.json559 B
03 SKILL.md 正文
Answer the question from the vault plus general knowledge, in one reply. Read-only.
Inputs
- Vault:
~/Documents/personal/obsidian/my-obsidian-notes. If it is missing, stop and say so. - Question: the user's question as asked. Do not read the vault's
CLAUDE.md; this skill holds the procedure.
Retrieval
The budget per firing is index.md, then at most 2 MOCs (Home MOC excluded), then at most 5
pages under wiki/ and notes/. Reading a page's summary: counts as opening it.
- Read
index.mdand pick the MOCs that fit the question. - Open at most 2 of them and pick pages from their links.
- For each page, read its
summary:first; read the body only if the summary fits. - If the links miss, grep
summary:,aliases:and filenames, and nothing else, then open hits within the same budget.
Stop when the budget is spent, even if more pages look relevant.
Answer
Give one merged answer. A claim taken from a page opened in this firing carries [[Page]]
inline; anything uncited is general knowledge. Cite only pages opened in this firing.
Not covered
If no opened page bears on the question, add exactly one line, Your vault doesn't cover this.,
and answer from general knowledge with no cites.
Conflicts
Where an opened note disagrees with the current view (a Bootstrap 4 note, say), add one line per
clash: Your note [[X]] says Y; current view is Z because W. Leave the note unchanged.
Keep
When the user says "keep this" or "save that", invoke to-vault with the answer as the Capture.
Never
- Write to the vault.
- Exceed the budget.
- Cite a page not opened in this firing.
04 同仓库更多 Skills
ingest
Ingest one external source (an article, course lesson, doc, PDF or URL) into the user's Obsidian vault: save the original to raw/, then build wiki/ pages per the vault's § Ingest. Use when the user types /ingest, or says "ingest this", "add this source to my wiki", "put this article/lesson in the vault as a wiki page". Works from any repo. Routing rule: someone else's words go to wiki/ (this skill); the user's own learnings and decisions go to notes/ (/to-vault).
to-tickets
Breaks a source into independently-grabbable GitHub tickets. For a code feature the source is the plan (`docs/plans/<feature>.md`, from /to-plan) and every new or changed symbol lands in exactly one ticket, its signatures copied into the ticket body; a non-code feature is cut from the PRD's slices. Cuts tickets for one feature per run. If a code feature has no approved plan, offers /to-plan instead of cutting from prose. In a repo that runs command-centre, also emits `[[task]]` blocks into its config; in a plain treepad repo, emits a Batch Manifest instead so the tickets materialise as stacked worktrees.
to-seams
Records an agreed-but-unlanded cross-repo interface as a seam: the file a consumer's agent gets pasted into its prompt as ground truth, plus the `[[seam]]` block command-centre reads for the retirement pointer. Use when two repos need to build against an interface neither has landed yet — "record a seam for X", "we agreed on this schema, seam it", "add a seam so Y can build against Z's new field". Halts for approval before writing either file.
to-roadmap
Prioritises settled features into a Now / Next / Later kanban board, rendered as a self-contained ./ideas/roadmap.html. Each card is a feature, not a ticket — one card later becomes several tickets via /to-prd -> /to-plan -> /to-tickets. Boards the features in ./docs/approach.md, or the "## Accepted ideas" in ./ideas/CONTEXT.md when there is no approach doc. The approach doc is settled truth: this assigns tiers and reasons about ordering, it never re-litigates what was decided.
to-prd
Turns one feature idea into a PRD built on journeys: a one-line problem, journeys (each ending in an observable state) and delivery slices that say what is usable after each. Interviews, explores the codebase, and saves to docs/prds/<feature>.md. Covers exactly one feature: given a multi-feature source, ask which one. Reads any approach doc or ideate report as priors so it doesn't re-ask what's settled, but needs none. Starts the per-feature spine (/to-prd -> /to-plan -> /to-tickets).
to-plan
Turns one feature's PRD into a skimmable plan in docs/plans/<feature>.md: a short overview, then per phase a glossary, the journeys it satisfies, and its new and modified definitions (types, enums, ports, schema), with the project:<slug> label. No code, branch or PR; the user's review of the file is the gate. Use for "plan this feature", "write the contract", "what are the types". One feature per run. Slash-only.