deepwiki
Query DeepWiki MCP to get AI-grounded answers about any public GitHub repository. Use when answering questions about a repo's source code, architecture, configuration, or internals. Triggers on "how does X work in <repo>", "deepwiki", "look up in codebase", "ask deepwiki", "check the source code".
Why use this skill?
Instantly query public GitHub repositories with DeepWiki. Get AI-grounded explanations, source code insights, and documentation summaries directly in OpenClaw.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/chunhualiao/deepwiki-mcpWhat This Skill Does
The DeepWiki MCP skill provides OpenClaw with the ability to query public GitHub repositories using AI-grounded insights. Instead of manual code exploration, this skill interfaces with the DeepWiki documentation service to retrieve explanations, architectural overviews, and source code analysis. It allows you to treat any public open-source project as a searchable, conversational knowledge base. Whether you are debugging an unfamiliar framework or trying to understand how a core module interacts with its dependencies, DeepWiki provides structured, reference-backed answers.
Installation
To install the DeepWiki MCP skill, use the ClawHub command-line interface provided in the OpenClaw environment:
clawhub install openclaw/skills/skills/chunhualiao/deepwiki-mcp
Ensure that your OpenClaw agent has permission to execute shell scripts located within the skill directory, as the agent relies on the deepwiki.sh wrapper to communicate with the MCP endpoint at https://mcp.deepwiki.com/mcp.
Use Cases
- Architecture Analysis: Understand the design patterns or module boundaries of a repository you have never worked on before.
- Quick Debugging: Get pointers to specific code paths or files that implement a feature when you encounter errors.
- Learning New Libraries: Use DeepWiki as an interactive tutorial to explore how a library handles specific tasks, such as authentication or state management.
- Documentation Discovery: Use the
topicsaction to map out the available documentation within a complex repository before diving into the code.
Example Prompts
- "How does the request routing mechanism work in the expressjs/express repository?"
- "Look up the authentication flow in the supabase/auth-js codebase."
- "Can you list the available documentation topics for the reactjs/react repo?"
Tips & Limitations
- Scope: This skill is strictly for public GitHub repositories. Private repositories are not supported.
- Latency: DeepWiki's indexing is not real-time. If you are inquiring about a commit made within the last 24-48 hours, the information may not yet be reflected in the service.
- Efficiency: While
docsprovides full content, it is often better to use theaskaction for targeted, high-precision answers.docscan produce large outputs that may clutter your chat history. - Fallback: If the provided helper script fails, you can perform direct queries against the MCP endpoint via standard
curlcommands, provided the agent environment has network access.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-chunhualiao-deepwiki-mcp": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, external-api
Related Skills
git-repo-to-book
Write a full-length technical book using multi-agent AI orchestration. Spawns parallel research, writing, and review agents to produce 60K-100K+ word manuscripts. Also supports revising individual chapters of existing books. Based on the real workflow that produced an 88,000-word, 14-chapter book in under 18 hours.
claude-usage
Check Claude Max plan usage limits by launching Claude Code and running /usage. Use when the user asks about Claude plan usage, remaining quota, rate limits, or sends /claude_usage.
skill-engineer
Design, test, review, and maintain agent skills for OpenClaw systems using multi-agent iterative refinement. Orchestrates Designer, Reviewer, and Tester subagents for quality-gated skill development. Use when user asks to "design skill", "review skill", "test skill", "audit skills", "refactor skill", or mentions "agent kit quality".
rose-container-tools
Build and run ROSE compiler tools using ROSE installed in a Docker container. Use when developing source-to-source translators, call graph analyzers, AST processors, or any tool that links against librose.so. Triggers on "ROSE tool", "callgraph", "AST traversal", "source-to-source", "build with ROSE", "librose".
task-runner
Persistent task queue system. Users add tasks at any time via natural language; tasks are stored in a single persistent queue file and executed asynchronously via subagents. A heartbeat/cron dispatcher wakes periodically to check pending tasks, spawn workers, and report completions. The system never "finishes" — it always remains ready for the next task.