Wiki query

Skill eliransu/digital-brain/skills/wiki-query

Answer questions using the Obsidian wiki vault. Reads hot cache first, then index, then relevant pages. Synthesizes answers with citations. Files good answers back as wiki pages. Supports quick, standard, and deep modes. Triggers on: what do you know about, query:, what is, explain, summarize, find in wiki, search the wiki, based on the wiki, wiki query quick, wiki query deep.From its SKILL.md

Install

npx -y skills add eliransu/digital-brain --skill wiki-query

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.5 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

wiki-query: Query the Wiki

The wiki has already done the synthesis work. Read strategically, answer precisely, and file good answers back so the knowledge compounds.

Query Modes

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

Quick Mode

Use when the answer is likely in the hot cache or index summary.

Read wiki/hot.md. If it answers the question, respond immediately.
If not, read wiki/index.md. Scan descriptions for the answer.
If found in index summary, respond and do not open any pages.
If not found, say "Not in quick cache. Run as standard query?"

Do not open individual wiki pages in quick mode.

Standard Query Workflow

Read wiki/hot.md first. It may already have the answer or directly relevant context.
Read wiki/index.md to find the most relevant pages (scan for titles and descriptions).
Read those pages. Follow wikilinks to depth-2 for key entities. No deeper.
Synthesize the answer in chat. Cite sources with wikilinks: (Source: [[Page Name]]).
Offer to file the answer: "This analysis seems worth keeping. Should I save it as wiki/synthesis/answer-name.md?"
If the question reveals a gap: say "I don't have enough on X. Want to find a source?"

Deep Mode

Use for synthesis questions, comparisons, or "tell me everything about X."

Read wiki/hot.md and wiki/index.md.
Identify all relevant sections (concepts, entities, sources, comparisons).
Read every relevant page. No skipping.
If wiki coverage is thin, offer to supplement with web search.
Synthesize a comprehensive answer with full citations.
Always file the result back as a wiki page. Deep answers are too valuable to lose.

Token Discipline

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.

Index Format Reference

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.

Domain Sub-Index Format

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.

Filing Answers Back

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.

Gap Handling

If the question cannot be answered from the wiki:

Say clearly: "I don't have enough in the wiki to answer this well."
Identify the specific gap: "I have nothing on [subtopic]."
Suggest: "Want to find a source on this? I can help you search or process one."
Do not fabricate. Do not answer from training data if the question is about the specific domain in this wiki.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most note taking skills give in ~1.2k tokens

Counted across 632 of the 857 authors here whose files we hold, read 2026-09-06

Use standard Markdown links for external URLsin 16 of 632, across 8 files
Use wikilinks for internal vault connectionsin 15 of 632, across 7 files
Embed content using the exclamation mark prefixin 14 of 632, across 6 files
Ask for clarification if the user request is ambiguousin 13 of 632
Add frontmatter properties at the top of the filein 12 of 632, across 4 files
Verify note renders correctly in reading viewin 12 of 632, across 4 files
Include a visual element on every slidein 11 of 632, across 5 files
Left-align body text and listsin 11 of 632, across 5 files
Maintain 0.5 inch minimum marginsin 11 of 632, across 5 files
Wrap formulas containing double quotes in single quotesin 11 of 632, across 5 files
Repeat one distinctive visual motif across all slidesin 10 of 632, across 4 files
Use 36pt or larger for slide titlesin 10 of 632, across 4 files

Said here and by no other author read

File valuable answers as new wiki pages
Scan section headers before reading index content
Use sub-indexes for domain-scoped queries
Offer to file answers after standard queries
Always file deep mode results as wiki pages
Update index.md and log.md after filing

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.