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'.
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."
/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)Launch the wiki-reader agent with the question and depth level.
.wiki/index.md, identify 2-4 relevant pagesbin/search-fulltext.py for ranked results[[slug]] referenceswiki_wikipedia_search for factual/encyclopedic topics, any MCP tools like Perplexity, Context7, etc.)wiki-writer agent (mode: ingest)[[slug]] citations.wiki/index.md only/wiki-readEverything in standard, plus:
.wiki/raw/ for source materials matching the queryThis 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 fetchbin/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 chainThe skill uses whatever is available — if the user has Perplexity MCP, it gets used. If they only have WebSearch, that works too.