Answers questions from Obsidian wiki vault using hot cache, index, and relevant pages. Synthesizes cited responses and files good answers back as wiki pages. Quick, standard, deep modes.
From claude-obsidiannpx claudepluginhub agricidaniel/claude-obsidian --plugin claude-obsidianThis skill uses the workspace's default tool permissions.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
The wiki has already done the synthesis work. Read strategically, answer precisely, and file good answers back so the knowledge compounds.
Three depths. Choose based on the question complexity.
| Mode | Trigger | Reads | Token cost | Best for |
|---|---|---|---|---|
| Quick | query quick: ... or simple factual Q | hot.md + index.md only | ~1,500 | "What is X?", date lookups, quick facts |
| Standard | default (no flag) | hot.md + index + 3-5 pages | ~3,000 | Most questions |
| Deep | query deep: ... or "thorough", "comprehensive" | Full wiki + optional web | ~8,000+ | "Compare A vs B across everything", synthesis, gap analysis |
Use when the answer is likely in the hot cache or index summary.
wiki/hot.md. If it answers the question, respond immediately.wiki/index.md. Scan descriptions for the answer.Do not open individual wiki pages in quick mode.
wiki/hot.md first. It may already have the answer or directly relevant context.wiki/index.md to find the most relevant pages (scan for titles and descriptions).(Source: [[Page Name]]).wiki/questions/answer-name.md?"Use for synthesis questions, comparisons, or "tell me everything about X."
wiki/hot.md and wiki/index.md.Read the minimum needed:
| Start with | Cost (approx) | When to stop |
|---|---|---|
| hot.md | ~500 tokens | If it has the answer |
| index.md | ~1000 tokens | If you can identify 3-5 relevant pages |
| 3-5 wiki pages | ~300 tokens each | Usually sufficient |
| 10+ wiki pages | expensive | Only for synthesis across the entire wiki |
If hot.md has the answer, respond without reading further.
The master index (wiki/index.md) looks like:
## Domains
- [[Domain Name]]: description (N sources)
## Entities
- [[Entity Name]]: role (first: [[Source]])
## Concepts
- [[Concept Name]]: definition (status: developing)
## Sources
- [[Source Title]]: author, date, type
## Questions
- [[Question Title]]: answer summary
Scan the section headers first to determine which sections to read.
Each domain folder has a _index.md for focused lookups:
---
type: meta
title: "Entities Index"
updated: YYYY-MM-DD
---
# Entities
## People
- [[Person Name]]: role, org
## Organizations
- [[Org Name]]: what they do
## Products
- [[Product Name]]: category
Use sub-indexes when the question is scoped to one domain. Avoid reading the full master index for narrow queries.
Good answers compound into the wiki. Don't let insights disappear into chat history.
When filing an answer:
---
type: question
title: "Short descriptive title"
question: "The exact query as asked."
answer_quality: solid
created: YYYY-MM-DD
updated: YYYY-MM-DD
tags: [question, <domain>]
related:
- "[[Page referenced in answer]]"
sources:
- "[[wiki/sources/relevant-source.md]]"
status: developing
---
Then write the answer as the page body. Include citations. Link every mentioned concept or entity.
After filing, add an entry to wiki/index.md under Questions and append to wiki/log.md.
If the question cannot be answered from the wiki: