wiki-query
Wiki Query
Ask a question. Read the wiki. Synthesize with citations. Offer to file the answer back.
Pre-condition
Find SCHEMA.md (search from cwd upward, or ~/wikis/). If not found, tell the user to run wiki-init first. Read it to get wiki root path and cross-reference convention.
Process
1. Read wiki/index.md first
Scan the full index to identify which pages are likely relevant. Do NOT answer from general knowledge — the wiki is the source of truth here, even if you think you know the answer.
2. Read relevant pages
Read the identified pages in full. Follow one level of [[slug]] links if they point to pages that seem relevant to the question.
3. Synthesize the answer
Write a response that:
- Is grounded in the wiki pages you read
- Cites inline using
[[slug]]for every claim sourced from a specific page - Notes agreements and disagreements between pages
- Flags gaps: "The wiki has no page on X" or "[[page]] doesn't cover Y yet"
- Suggests follow-up sources to ingest or questions to investigate
Format for the question type:
- Factual → prose with citations
- Comparison → table
- How-it-works → numbered steps
- What-do-we-know-about-X → structured summary with open questions
4. Always offer to save
After answering, say:
"Worth saving as
wiki/pages/<suggested-slug>.md?"
If yes:
- Write the page with frontmatter:
tags: [query, analysis],sources: [all cited slugs] - Add entry to
wiki/index.mdunder the correct category (Analyses or similar) - Append to
wiki/log.md:## [<today>] query | <question summary> Filed as: [[<slug>]]
If no:
- Append to
wiki/log.md:## [<today>] query | <question summary> Not filed.
Common Mistakes
- Answering from memory — Always read the wiki pages. The wiki may contradict what you think you know, and that contradiction is valuable signal.
- Skipping the save offer — Good query answers compound the wiki's value. Always offer.
- No citations — Every factual claim should trace back to a
[[slug]].
More from kfchou/wiki-skills
wiki-lint
Use when auditing a wiki for health issues — contradictions between pages, orphan pages, broken cross-references, stale claims, missing pages, or coverage gaps. Run after every 5-10 ingests.
46wiki-update
Use when revising existing wiki pages because knowledge has changed, a new piece of information updates or contradicts existing content, or the user wants to directly edit wiki content with LLM assistance.
45wiki-init
Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.
45wiki-ingest
Use when adding a new source to a wiki — a paper, article, URL, file, transcript, or any document. One ingest may touch 10-15 wiki pages.
45wiki-audit
Use when fact-checking a single wiki page against its cited sources — verifies that every footnote actually supports its claim and surfaces uncited factual claims. Run after ingesting a high-stakes page or any time you want confidence in one page's accuracy.
26