deepwiki — Claude Code skill: GitHub repo docs from the terminal
A skill that pulls documentation for any public GitHub repo through DeepWiki: table of contents, full wiki text, and answers to questions about the code.
npx skills add seflless/deepwiki --skill deepwiki -a claude-codeWhat deepwiki does
The skill wraps the @seflless/deepwiki CLI, which queries DeepWiki for docs on public repos. Three commands: toc returns the table of contents, wiki dumps the full wiki, ask answers a specific question about the code. You can ask about several repos at once, up to 10 per call, which helps when you need to see how two libraries fit together.
Inside are the command and flag tables the skill fills in for you. --json gives raw JSON for parsing, -q hides spinners, --no-color turns off colors. It suggests starting with toc to see which sections exist, then asking specifics through ask.
Node.js is required, since the commands run through npx. No Node means the skill won't start, so check that before sending your agent off to look up docs.
What it helps with
- see the doc structure of an unfamiliar library
- dump a repo's full wiki as JSON
- ask a question about someone else's source code
- compare how two libraries are built
- save docs to a file for later reading
Example prompts for the agent
- look up the docs for facebook/react with deepwiki
- ask deepwiki how the tool permission system works in anthropics/claude-code
- compare server components in facebook/react and vercel/next.js via deepwiki
How to install deepwiki
1Skills CLI (Vercel)
npx skills add seflless/deepwiki --skill deepwiki -a claude-code2Manually: put the files in place
~/.claude/skills/deepwiki/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/deepwiki/
1Skills CLI (Vercel)
npx skills add seflless/deepwiki --skill deepwiki -a codex2Manually: put the files in place
.agents/skills/deepwiki/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add seflless/deepwiki --skill deepwiki -a cursor2Manually: put the files in place
.cursor/skills/deepwiki/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install seflless/deepwiki deepwiki2Manually: put the files in place
.github/skills/deepwiki/SKILL.md1Skills CLI (Vercel)
npx skills add seflless/deepwiki --skill deepwiki -a gemini-cli2Platform CLI
gemini skills install https://github.com/seflless/deepwiki --path skills/deepwikiManually: put the files in place
.devin/skills/deepwiki/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add seflless/deepwiki --skill deepwiki -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about deepwiki
How do I install deepwiki in Claude?
Run npx skills add seflless/deepwiki --skill deepwiki -a claude-code. The skill lands in ~/.claude/skills/deepwiki/SKILL.md.
What does deepwiki do?
It fetches documentation for public GitHub repos through DeepWiki: table of contents, full wiki text, and answers to code questions. Works from the terminal and from an agent.
What does deepwiki need to run?
Node.js, because the commands run through npx. You can ask about several repos at once, up to 10 per call.
Source text
SKILL.md · MIT
--- name: deepwiki description: > 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". --- # 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 ```bash # 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 `--json` when you need structured data to parse - Use `toc` first to understand what docs exist, then `ask` for specifics - Multi-repo `ask` is great for understanding how libraries interact
© seflless · MIT · seflless/deepwiki
