explore
Read-only codebase exploration: discovery, structural reading, and emission of architecture/pattern/tooling/dependency summaries. Use to understand existing code, map files, trace function flow, locate symbols, or build pre-implementation context. Defers to ODIN's Dispatch-First protocol (1/3/5 Explore-agent escalation). Trigger on \"explore\", \"find where X is\", \"how does X work in the code\", \"map the codebase\", \"what files handle Y\", or any architecture/pattern/tooling/dependency context request on a local repo — even without naming /explore.
npx skills add majiayu000/claude-skill-registry --skill explore --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Explore Command Read-only codebase orientation. Emit architecture, pattern, tooling, and dependency summaries for a repo-local task. Do NOT write, edit, or commit files. ## When to Apply / NOT **Apply:** - Pre-implementation codebase orientation (feature, fix, refactor) - File and symbol mapping — "where is X defined", "what uses Y" - Architectural surveys — module boundaries, control flow, coupling - Dependency tracing — import graphs, transitive deps, config files **NOT apply:** - External library docs, SDK APIs, or framework behavior — use a doc-retrieval workflow instead - User wants a packed repo file as a deliverable artifact - Implementation, editing, or committing anything ## Process 1. **Scope** — parse the task. Identify files/dirs/concerns. State scope explicitly before dispatching. 2. **Dispatch decision** — for multi-file or uncertain tasks: dispatch Explore agent(s) instead of reading directly. Escalation: 1 agent for single-concern known scope; 3 agents for multiple concerns or unknown scope; 5 agents for cross-module or architectural survey. Auto-skip (direct reads allowed) only for single file under 50 LOC. 3. **Discovery** — token-efficient flags mandatory: - Fi
- When to Apply / NOT
- Process
- Required Output
- Task Understanding
- Architecture Context
- Pattern Context
- Tooling Context
- Dependency Map
- Critical Files Summary
- Constraints & Considerations
- Recommended Next Steps
- Tool Restrictions
- Anti-Patterns
What does the explore skill do?
Read-only codebase exploration: discovery, structural reading, and emission of architecture/pattern/tooling/dependency summaries. Use to understand existing code, map files, trace function flow, locate symbols, or build pre-implementation context. Defers to ODIN's Dispatch-First protocol (1/3/5 Explore-agent escalation). Trigger on \"explore\", \"find where X is\", \"how does X work in the code\", \"map the codebase\", \"what files handle Y\", or any architecture/pattern/tooling/dependency context request on a local repo — even without naming /explore.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill explore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.