skills/deepwiki/SKILL.md
Query DeepWiki for repository documentation and structure. Use to understand open source projects, find API docs, and explore codebases.
npx skillsauth add petekp/claude-skills deepwikiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query DeepWiki for AI-generated documentation about any public GitHub repository.
DeepWiki (deepwiki.com) provides AI-generated documentation for GitHub repositories, including:
URL Pattern: Replace github.com with deepwiki.com in any repo URL:
github.com/vercel/next.js → deepwiki.com/vercel/next.jsDeepWiki provides a free MCP server with no authentication required for public repos.
claude mcp add -s user -t http deepwiki https://mcp.deepwiki.com/mcp
Add to your MCP config:
{
"mcpServers": {
"deepwiki": {
"serverUrl": "https://mcp.deepwiki.com/sse"
}
}
}
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 |
# Fetch documentation overview
WebFetch https://deepwiki.com/owner/repo "Summarize the architecture"
# Example
WebFetch https://deepwiki.com/vercel/next.js "How does routing work?"
Use the MCP tools directly:
mcp__deepwiki__read_wiki_structure - Get repo structuremcp__deepwiki__read_wiki_contents - Get documentationmcp__deepwiki__ask_question - Ask questionsIf DeepWiki lacks coverage for a repo, use GitHub API:
gh api repos/owner/repo | jq '{description, language, topics, stars: .stargazers_count}'
gh api repos/owner/repo/readme --jq '.content' | base64 -d
gh api repos/owner/repo/git/trees/main?recursive=1 | \
jq -r '.tree[] | select(.type == "blob") | .path' | head -50
Two protocols are supported:
https://mcp.deepwiki.com/sse - Official MCP spechttps://mcp.deepwiki.com/mcp - Cloudflare/OpenAI compatibledevelopment
Draft short, plainspoken notes in the author's voice that help reviewers understand non-obvious choices, boundaries, and preserved behavior in the author's own pull request or local diff. Use when the user asks to self-review, annotate, or add reviewer context to their PR or changes. Draft locally when no PR exists, and post approved notes as one GitHub review when a PR does exist. Do not use for reviewing someone else's PR, writing code comments, explaining code generally, or drafting a PR description. Never post without explicit approval.
tools
Design and build pure-CSS (zero-JavaScript) Tailwind CSS v4 plugins of unusual depth and craft. Use when the user wants to create, architect, or refine a Tailwind utility plugin or CSS effect — e.g. "make a tailwind plugin", "build a tw-* plugin", "a CSS-only shimmer/fade/glow/grain/noise utility", "tailwind v4 @utility", "package this effect as a plugin", or wants an effect with surprising visual depth (gradients, masks, filters, SVG filter tricks, scroll-driven animation). Pairs deep CSS/SVG technique research with a bespoke tuning workbench for dialing the effect in. Inspired by tw-fade and tw-shimmer.
content-media
Create clear, polished before-and-after screenshots for a GitHub pull request. Use when a UI change needs visual proof: capture matching states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
testing
--- name: latent-potential description: First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this be