wiki-query
Skill1 starsChanged 37 days agoMITView on GitHub
Answer a question from the wiki, with citations, and say what the wiki does not cover. Reads only. Use for what does the wiki say, explain from my notes, find in the wiki, what do we know about X, which repositories use Y. Keeping the answer is wiki-save; a reading list of the documents on a subject is wiki-checkout.
41 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- barakgut/llm-wikitheir own version, first seen Nov 1, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
- wareagledusty/wiki-federation-starter-kitedited, first seen Nov 1, 2026
- ProduktEntdecker/enterprise-memory-startertheir own version, first seen Nov 1, 2026
- hmjBill/skillstheir own version, first seen Oct 29, 2026
Used with
Projects with it also use wiki-capture, wiki-update and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jehrhardtSkillwiki-capture
Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.
Also in 6 projects that use this
bozhouDevSkillwiki-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.
Also in 9 projects that use this
Ivy-Chen1999Skillwiki-setup
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.
Also in 5 projects that use this
- Ivy-Chen1999Skill
wiki-research
Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced knowledge on a topic filed directly into their wiki.
Also in 4 projects that use this
- bozhouDevSkill
wiki-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.
Also in 7 projects that use this
- +5 more from Ivy-Chen1999
Other versions41 projects use a version of this.
Word for word · 2
- nathanaday/almagest★ 1100% same
- nathanaday/atlas-obsidian★ 1100% same
Edited · 1
- wareagledusty/wiki-federation-starter-kit★ 110% same
Wrote their own version · 38
- AgriciDaniel/claude-obsidian★ 16ksame name
- Ar9av/obsidian-wiki★ 3.7ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- kfchou/wiki-skills★ 189same name
- bozhouDev/bozhou-skills★ 78same name
- vanillaflava/llm-wiki-skills★ 65same name
- cookyman74/llmwiki-harness★ 34same name
- Ivy-Chen1999/llm-wiki-kit★ 21same name
- CarbeneAI/Forge★ 9same name
- CodePhobiia/claude-roblox-game-studio★ 9same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- almagest-onboardSkill
- almagestSkill
- repo-ingestSkill
- repo-linkSkill
- repo-unlinkSkill
- wiki-checkoutSkill
- wiki-editSkill
- wiki-ingestSkill
- wiki-mapSkill
- wiki-reviewSkill
- wiki-saveSkill
- wiki-syncSkill
- wiki-wikifySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 31 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Call search. A document must hold every tag, or a tag below it.
- Distinctive: line 28
When the user wants to browse a tag rather than ask, link the tag's page (its overview topic or repository page): it lists the documents …
- Distinctive: line 30
Read the best documents with Read.
“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
wiki-query
The wiki holds what the vault knows, each claim cited. This skill turns a question into a search with tags, reads the documents that answer it, and answers with a citation for each claim, keeping the wiki's claims apart from your own reasoning.
Tools: search, context, and Read.
Procedure
- Turn the question into a query. Words that name tags in the vocabulary (the tag
list in the session-start context, or
vault) becometags: "my cs513 self-driving project" →tags: [school/cs513, self-driving, project]. The rest istext. Addtypesorkindswhen the question asks for one ("which policies…" →types: [topic],kinds: [policy]). - Call
search. A document must hold every tag, or a tag below it. When the hits are many, readfacets.tagsand add the tag that splits them;facets.typesandfacets.statusnarrow the same way. When there are no hits, drop the least certain tag and search again. Say which tags you used. - For a question about repositories ("which services use MQTT"), call
contextwith thetags, or withrepositoryfor one repository. Read the tag pages'## Contextinpages, and therepositoriesandpoliciesit lists. When the user wants to browse a tag rather than ask, link the tag's page (its overview topic or repository page): it lists the documents under the tag. - Read the best documents with Read. Follow a link one hop when the answer needs it.
- Answer. Cite each claim with its document (
[[Topic]]), and through the topic its source. Keep the wiki's claims apart from your own reasoning, and mark the reasoning as yours. - Say what the wiki lacks, when it lacks something the question needs. Do not fill the gap from general knowledge without saying so.
Gate
None. The skill writes nothing.
Hand off
wiki-save when the answer is new synthesis the user wants kept. wiki-checkout when the user wants to read the material itself: a reading list and copies to mark up. almagest when the question turns into work in a repository.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.