Wiki Ingest
Use this skill for one-source-at-a-time wiki ingestion.
First principle
Treat the workspace as a persistent knowledge base. You are not answering a one-off question. You are updating the durable markdown artifact.
Use the vault tool first
Before making wiki changes, inspect the existing note graph with interpreter_vault.
Preferred sequence:
interpreter_vaultwithaction="snapshot"to confirm note count and workspace shape.interpreter_vaultwithaction="search_notes"for the key entities, concepts, and source title you expect to touch.interpreter_vaultwithaction="note_context"for the most relevant existing pages before editing them.- Read the actual markdown files you need to update.
Do not re-derive backlinks, aliases, or tags with ad hoc grep when the vault tool already has the graph.
If that inspection shows there is not yet a real wiki or established vault workflow to ingest into, stop and use $wiki-bootstrap first instead of inventing structure ad hoc inside the ingest pass.
Ingest workflow
- Read the source fully.
- Summarize the key takeaways briefly for the user if the angle is unclear or if confirmation is useful.
- Create or update the source page.
- Update every related entity, concept, synthesis, or comparison page that the source materially changes.
- Add
[[wikilinks]]for every durable connection. - Update
index.md. - Append a grep-friendly entry to
log.md. - Report which pages were created, updated, or flagged for contradiction.
Hard rules
- Never modify
raw/. - Respect an existing vault structure instead of forcing
raw/+wiki/if the user already has one. - If there is no durable wiki structure yet, use
$wiki-bootstrapfirst. - Always use
[[wikilinks]]for inter-wiki references. - Flag contradictions explicitly instead of silently resolving them.
- Update
index.mdandlog.mdon every ingest. - Prefer touching all materially affected pages over doing the minimum possible.