Agent skill
deepwiki
Query DeepWiki for repository documentation and structure. Use to understand open source projects, find API docs, and explore codebases.
Install this agent skill to your Project
npx add-skill https://github.com/petekp/claude-code-setup/tree/main/skills/deepwiki
SKILL.md
DeepWiki - Repository Documentation
Query DeepWiki for AI-generated documentation about any public GitHub repository.
Overview
DeepWiki (deepwiki.com) provides AI-generated documentation for GitHub repositories, including:
- Repository structure and architecture
- API documentation
- Code explanations
- Interactive diagrams
Quick Start
URL Pattern: Replace github.com with deepwiki.com in any repo URL:
github.com/vercel/next.js→deepwiki.com/vercel/next.js
MCP Server Setup
DeepWiki provides a free MCP server with no authentication required for public repos.
Add to Claude Code (one-time setup)
claude mcp add -s user -t http deepwiki https://mcp.deepwiki.com/mcp
For Cursor/Windsurf
Add to your MCP config:
{
"mcpServers": {
"deepwiki": {
"serverUrl": "https://mcp.deepwiki.com/sse"
}
}
}
Available MCP Tools
Once configured, these tools become available:
| Tool | Purpose |
|---|---|
read_wiki_structure |
Get documentation topics/structure for a repo |
read_wiki_contents |
Retrieve actual documentation content |
ask_question |
Ask AI-powered questions about the repo |
Usage Examples
Via WebFetch (works immediately)
# Fetch documentation overview
WebFetch https://deepwiki.com/owner/repo "Summarize the architecture"
# Example
WebFetch https://deepwiki.com/vercel/next.js "How does routing work?"
Via MCP (after setup)
Use the MCP tools directly:
mcp__deepwiki__read_wiki_structure- Get repo structuremcp__deepwiki__read_wiki_contents- Get documentationmcp__deepwiki__ask_question- Ask questions
Fallback: GitHub + AI
If DeepWiki lacks coverage for a repo, use GitHub API:
Get Repository Overview
gh api repos/owner/repo | jq '{description, language, topics, stars: .stargazers_count}'
Get README
gh api repos/owner/repo/readme --jq '.content' | base64 -d
Get File Structure
gh api repos/owner/repo/git/trees/main?recursive=1 | \
jq -r '.tree[] | select(.type == "blob") | .path' | head -50
Wire Protocols
Two protocols are supported:
- SSE at
https://mcp.deepwiki.com/sse- Official MCP spec - HTTP at
https://mcp.deepwiki.com/mcp- Cloudflare/OpenAI compatible
Best Practices
- Use WebFetch first - Works without MCP setup
- Check if repo is indexed - Popular repos have better coverage
- Ask specific questions - DeepWiki excels at targeted queries
- Fall back to GitHub - For unindexed or private repos
Limitations
- Public repos only - Private repos require Devin account
- Coverage varies - 50,000+ popular repos indexed
- No authentication - Can't access private documentation
Resources
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
manage-codex
Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
capture-learning
Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.
agent-changelog
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
Didn't find tool you were looking for?