Clone and explore external GitHub repositories to understand how libraries, frameworks, or dependencies work. Use when user provides a GitHub URL (github.com/owner/repo), asks "how does X library work", wants to look at source code for a dependency, asks about implementation details of an external package, or says "explore", "look at", or "check out" a repository. Automatically checks out the matching version tag when the repo is a dependency in the current project.
Clone and explore external GitHub repositories to understand how libraries, frameworks, or dependencies work. Use when user provides a GitHub URL, asks "how does X library work", wants to look at source code for a dependency, or asks about implementation details of an external package.
/plugin marketplace add abatilo/vimrc/plugin install abatilo-core@abatilo-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
update-reference.mdversion-detection.mdExplore external GitHub repositories by cloning them locally and using the Explore agent for comprehensive codebase analysis.
~/.cache/claude/repos/<owner>/<repo>/
Extract owner and repo from various formats:
https://github.com/owner/repogit@github.com:owner/repo.gitowner/repo (shorthand)github.com/owner/repols ~/.cache/claude/repos/<owner>/<repo>/
update-reference.md)mkdir -p ~/.cache/claude/repos/<owner>
git clone https://github.com/<owner>/<repo>.git ~/.cache/claude/repos/<owner>/<repo>
Before exploring, check if this repo is a dependency in the current working directory.
Consult version-detection.md for:
If a matching version is found:
cd ~/.cache/claude/repos/<owner>/<repo>
git fetch --all --tags
git checkout <tag>
Common tag formats to try:
v1.2.31.2.3release-1.2.3release/1.2.3ALWAYS use the Task tool with subagent_type=Explore for answering questions about the repository.
Do NOT manually browse files when the Explore agent can do it. The Explore agent is optimized for:
Example:
Task(
subagent_type="Explore",
prompt="""In ~/.cache/claude/repos/owner/repo/, find how authentication is implemented.
Requirements for your response:
- Include code snippets with file paths and line numbers
- Show key type definitions and function signatures
- End with a 'Key Files for Further Exploration' table with columns: File, Purpose, Start Here If...
"""
)
When answering questions about the repository, responses MUST include:
// File: pkg/controller/foo.go:42-58
func (r *Reconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctrl.Result, error) {
// ... relevant code
}
At the end of every response, include a "Key Files for Further Exploration" section:
## Key Files for Further Exploration
| File | Purpose | Start Here If... |
|------|---------|------------------|
| `pkg/apis/v1/types.go` | Core type definitions | You want to understand the data model |
| `pkg/controller/main_controller.go` | Main reconciliation logic | You want to understand the control flow |
| `docs/design.md` | Architecture decisions | You want high-level understanding |
Guidelines for file recommendations:
1. Brief answer summary (2-3 sentences)
2. Detailed explanation with inline code snippets
3. Architecture/flow diagrams if helpful (ASCII or description)
4. Key Files for Further Exploration table
5. Optional: Related topics the user might want to explore next
For refreshing the repository or switching versions, consult update-reference.md.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.