Use when the user asks questions about a GitHub repository's architecture, API, or internals, or mentions deepwiki-cli or DeepWiki. Activates when the user needs to understand a codebase they haven't cloned locally, or asks how a library or framework works. Do NOT activate for local codebases already accessible on disk or private repositories. --- # deepwiki-cli Skill deepwiki-cli provides AI-generated wiki documentation for GitHub repositories. Use the `deepwiki-cli` to query it directly — this keeps only the result text in Claude's context, avoiding MCP protocol overhead. ## When This Skill Activates - User references a GitHub repository by name (owner/repo format) - User asks how a library or framework works - User needs to understand a codebase they haven't read locally - User asks architecture or API questions about an open-source project ## How to Use Run via `Bash` tool: ```bash # Ask a question about a repository deepwiki-cli ask <owner/repo> "<question>" # List wiki topics for a repository deepwiki-cli structure <owner/repo> # Read full wiki contents deepwiki-cli read <owner/repo> ``` ## Examples ```bash deepwiki-cli ask facebook/react "How does the reconciler work?" deepwiki-cli ask vercel/next.js "What is the App Router architecture?" deepwiki-cli structure rust-lang/rust deepwiki-cli read tokio-rs/tokio ``` ## Prerequisites The `deepwiki-cli` binary must be installed: ```bash cargo install deepwiki-cli ``` If the binary is not found, inform the user to install it first. ## When NOT to Use - Repository is already cloned locally — use Glob/Grep/Read tools directly - Repository is private — deepwiki-cli only works with public repositories - User is asking about their own code in the current working directory ## Error Handling If `deepwiki-cli` is not installed or a command fails: 1. Check if the binary exists: `which deepwiki-cli` 2. If not found, tell the user to install: `cargo install deepwiki-cli` 3. If the repository is not found, verify the owner/repo
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
Upload archive: .zip / .skill (recommended)
Upload skills folder
Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
Claude Code:~/.claude/skills/
Codex CLI:~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared across tools?
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
Wrong folder path or nested one level too deep
Invalid/incomplete SKILL.md fields or format
Dependencies missing (Python/Node/CLI)
Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills: