- Add compiled wiki maintenance, retrieval lint, and packet promotion steps to knowledge-gardener skill - Restructure research-vault workflow with source ingest, answer filing, and pre-completion lint pass - Add Log.md for tracking ingest, queries, and corrections - Enhance Claims template with provenance, supports/contradicts, and confidence tracking - Add Compiled Pages table and Raw Source Rules to packet template - Enhance atomic notes with frontmatter, promotion status, and structured links - Distinguish source claims, synthesis, user opinions, and open questions throughout This implements a Karpathy-style compiled wiki approach where raw sources stay immutable, packet notes are the maintained synthesis layer, and reusable notes can be promoted to the main vault.
4.5 KiB
4.5 KiB
name, description, metadata, disable-model-invocation
| name | description | metadata | disable-model-invocation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| knowledge-gardener | Run vault-aware semantic search, synthesis, note creation, linking, and Zettelkasten workflows for this Obsidian vault. |
|
true |
Purpose
This skill turns your agent into a vault-aware Obsidian knowledge gardener. It prioritizes semantic retrieval, clear note structure, safe incremental edits, and useful internal links.
Vault Conventions
- Preserve folder casing and names used in this vault:
Inbox/,Dailies/,projects/,resources/,archive/,Templates/. - Use Obsidian wikilinks:
[[Note Title]]. - Keep existing frontmatter schema compatible with existing notes:
---
id: <slug-or-date-id>
aliases: []
tags: []
area: ""
project: ""
---
- Default location for new AI-generated notes is
Inbox/unless explicitly asked otherwise.
Core Workflows
-
Semantic Search
- Use
python tools/obsidian_semantic_query.py --vault-root . --query "..." --k 12. - Return ranked notes with short relevance rationale.
- Use
-
Summarization
- Retrieve nearest notes first, then synthesize.
- Include conflicts, unknowns, and suggested next notes.
-
New Note Creation
- Create with canonical frontmatter.
- Include
## Summaryand optional scaffold sections. - If a summary is provided, include it verbatim under
## Summary.
-
Automatic Linking
- Suggest links from semantically related notes.
- Prefer high-signal links (shared concepts, same project/area, repeated terms).
-
Refactor to Atomic Notes
- Split long mixed-topic notes into smaller notes.
- Keep parent note as a structure note and link to children.
-
Metadata Maintenance
- Keep
id,aliases,tags,area,projectvalid. - Suggest tags from note content; avoid noisy tag spam.
- Keep
-
Research Capture
- Store source summary in vault.
- Extract key claims, evidence, confidence, and follow-up questions.
- Distinguish raw source claims, agent synthesis, user opinions, and open questions.
- Convert durable insights into permanent notes.
-
Compiled Wiki Maintenance
- For bounded research topics, maintain a Karpathy-style compiled wiki layer: immutable raw sources → maintained concept/claim/synthesis notes → retrievable answers.
- On ingest, update existing pages before creating duplicates; the graph should get denser, not just larger.
- File durable query answers back into notes, then add or update links from indexes/MOCs.
- Keep a lightweight log of ingests, filed answers, lint passes, promotions, and major corrections when the folder has a
Log.mdor equivalent.
-
Retrieval Lint
- Check for unsupported claims, stale or contradictory claims, orphan notes, missing backlinks, missing glossary terms, and unanswered questions.
- Verify a future agent can answer the main question from the maintained notes without rereading raw sources.
-
Packet Promotion
- Treat research packets as incubators and the main vault as the indexed library.
- Promote notes only when they are reusable beyond the packet, stand alone, have evidence/provenance, and connect to existing vault concepts.
- Leave a link behind in the packet and update relevant indexes/MOCs.
- Zettelkasten Conversion
- Convert source note into atomic permanent notes.
- Add explicit links and one short structure note (MOC-lite) when useful.
Quality Guardrails
- Never delete user content unless explicitly requested.
- Prefer additive edits and clear section boundaries.
- Keep writing concise and skimmable.
- Keep tags focused and reusable.
- Keep citations close to claims; do not let synthesized notes obscure source provenance.
- Before finalizing research edits, run a retrieval check: likely future questions should have obvious entry points through indexes, links, claims, or glossary terms.
- Rebuild semantic index after major note creation/refactor sessions.
Operational Commands
- Build index:
python tools/obsidian_semantic_index.py --vault-root . - Query index:
python tools/obsidian_semantic_query.py --vault-root . --query "your query" --k 12 - Frontmatter lint:
python tools/obsidian_semantic_maintain.py lint --vault-root . - Related notes:
python tools/obsidian_semantic_maintain.py related --vault-root . --note "Inbox/your-note.md" --k 8
Trigger Hints
Load this skill when the user asks to search, summarize, connect, refactor, or organize Obsidian notes.