| name | ask |
| description | Use when the user asks an in-depth question about a GitHub repository's internals, architecture, or implementation details — anything that benefits from AI-summarized repo documentation rather than raw code reading. Triggers on phrases like "how does <repo> handle X", "explain the architecture of <repo>", "what's inside <owner/repo>", or "compare <repoA> and <repoB>". Wraps the DeepWiki MCP (`mcp__deepwiki__read_wiki_structure` / `read_wiki_contents` / `ask_question`). |
DeepWiki ask
Deep query a GitHub repository using DeepWiki's AI-powered documentation. Same workflow as the /deepwiki:ask slash command — this skill exposes it as a capability so the model can reach for it during conversational research.
- Restate the repository (
owner/repo) and the question back to the user so the parse is auditable.
- Follow the four-phase procedure (structure → optional contents → ask → optional multi-query expansion).
- Return the answer in the documented output format.
See references/ask-procedure.md in this plugin's installed root for the full workflow, smart-query strategy, multi-repo patterns, and error handling table. Under Claude Code this resolves to ${CLAUDE_PLUGIN_ROOT}/references/ask-procedure.md; under Codex 0.135 (which does not export CLAUDE_PLUGIN_ROOT) the plugin cache directory exposes the same references/ subdirectory next to skills/ (~/.codex/plugins/cache/<marketplace>/deepwiki/<version>/references/); under Hermes it is $HERMES_HOME/plugins/deepwiki/references/ (plugin install). This reference is a plugin-root file (shared with the generate-llmstxt skill), so a skill-level install carries it only when the whole plugin is installed.
Requirements
- DeepWiki MCP must be configured in the host runtime (
mcp__deepwiki__* tools available). If absent, surface the setup link: https://mcp.deepwiki.com/.
- Internet connection (queries the DeepWiki API).
