Query any public GitHub repo's documentation via DeepWiki. Use when needing to understand a library, framework, or dependency. Triggers on "look up docs", "how does X work", "deepwiki", "deepwiki".
Install
npx skills add https://github.com/seflless/deepwiki --skill deepwikiSKILL.md
deepwiki
Query any public GitHub repo's docs from the terminal via DeepWiki. Assumes Node.js is installed.
Commands
| Command | Usage | Description |
|---|---|---|
toc |
npx @seflless/deepwiki toc <owner/repo> |
Table of contents |
wiki |
npx @seflless/deepwiki wiki <owner/repo> |
Full wiki content |
ask |
npx @seflless/deepwiki ask <owner/repo> "<question>" |
AI-powered Q&A |
ask |
npx @seflless/deepwiki ask <repo1> <repo2> "<question>" |
Multi-repo Q&A (max 10) |
Flags
| Flag | Purpose |
|---|---|
--json |
Raw JSON output (good for piping) |
-q, --quiet |
No spinners/progress |
--no-color |
Disable colors |
Examples
# Understand a library's structure
npx @seflless/deepwiki toc facebook/react
# Get full docs for reference
npx @seflless/deepwiki wiki oven-sh/bun --json > bun-docs.json
# Ask a specific question
npx @seflless/deepwiki ask anthropics/claude-code "How does the tool permission system work?"
# Cross-project question
npx @seflless/deepwiki ask facebook/react vercel/next.js "How do server components work across these projects?"
Tips
- Use
--jsonwhen you need structured data to parse - Use
tocfirst to understand what docs exist, thenaskfor specifics - Multi-repo
askis great for understanding how libraries interact
Related skills
domain-modelingmattpocock714KBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.to-specmattpocock576KTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.caveman-helpjuliusbrussee369KQuick-reference card for caveman modes, skills and commands. Trigger: /caveman-help or "caveman help".pptxanthropics228KUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the u