wiki-read
Skill50 starsChanged 7 months agoMITView on GitHub
Search and query the wiki — get cited answers, with automatic research when knowledge is missing. Three depth modes. Use when: 'check wiki', 'what do we know about', 'look up', 'find in wiki', 'search wiki', 'search for', 'find information about', 'do we have notes on', 'wiki context', 'existing knowledge', 'research', 'look into', 'find out about', 'investigate', 'what is', 'how does X work'.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- wicii2120/skillstheir own version, first seen Aug 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- wicii2120/skills★ 1same name
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 repository4 other files it gives its agents.
- wiki-maintainSkill
- wiki-serveSkill
- wiki-viewSkill
- wiki-writeSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Ask the wiki a question and get a cited answer.
- Very specific: line 23
Read .wiki/index.md, identify 2-4 relevant pages
- Very specific: line 24
Use bin/search-fulltext.py for ranked results
- Very specific: line 25
Read the relevant pages, synthesize a cited answer with [[slug]] references
- Distinctive: line 28
Search using available tools, fetch and extract content
- Distinctive: line 38
No page content read, no research fallback — fastest possible response
- Very specific: line 39
If not found, suggest running standard /wiki-read
- Very specific: line 43
Search .wiki/raw/ for source materials matching the query
- Distinctive: line 45
Use all available tools iteratively for multi-channel research if needed
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wiki Read
Ask the wiki a question and get a cited answer. If the wiki doesn't have the answer, automatically researches using whatever tools are available, ingests the results, and answers from the new pages.
Resolve .wiki/ from plugin install scope. If not found, say "No wiki found. Use /wiki-write to create one."
Arguments
/wiki-read <question>— standard: search wiki first, research if not found, answer with citations/wiki-read quick <question>— index scan only, no research fallback (fastest)/wiki-read deep <question>— full wiki search + raw sources + automatic multi-channel research if needed (most thorough)
Process
Launch the wiki-reader agent with the question and depth level.
Standard depth (default)
- Read
.wiki/index.md, identify 2-4 relevant pages - Use
bin/search-fulltext.pyfor ranked results - Read the relevant pages, synthesize a cited answer with
[[slug]]references - If NOT found or insufficient: automatically research using whatever tools are available:
- Discover available tools at runtime (WebSearch, WebFetch,
wiki_wikipedia_searchfor factual/encyclopedic topics, any MCP tools like Perplexity, Context7, etc.) - Search using available tools, fetch and extract content
- Ingest results via
wiki-writeragent (mode: ingest) - Answer from the newly created pages with
[[slug]]citations - Note: "Researched fresh and saved to wiki."
- Discover available tools at runtime (WebSearch, WebFetch,
- Offer to save analysis as a wiki page if the answer is substantial
Quick depth
- Read
.wiki/index.mdonly - Scan for matching slugs/titles by text match
- Return: list of relevant pages with one-line descriptions
- No page content read, no research fallback — fastest possible response
- If not found, suggest running standard
/wiki-read
Deep depth
Everything in standard, plus:
- Search
.wiki/raw/for source materials matching the query - Cross-reference raw sources with compiled pages
- Use all available tools iteratively for multi-channel research if needed
- Most thorough — uses the most context
Tool Discovery
This skill works with whatever tools the user has. No hardcoded channels or services.
Available tools are discovered at runtime:
WebSearch/WebFetch— Claude Code built-in web search and fetch- Any MCP search tools (Perplexity, Exa, Tavily, etc.)
bin/search-academic.py— Semantic Scholar, arXiv, OpenAlex, CrossRef (if available)bin/search-code.py— GitHub, npm, PyPI, Stack Overflow (if available)bin/fetch.py— content extraction chain
The skill uses whatever is available — if the user has Perplexity MCP, it gets used. If they only have WebSearch, that works too.
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.