New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Explore

by parcadei in parcadei/Continuous-Claude-v3

Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)

MITAuto-check: notes

Install Explore

skills CLI
$ npx skills add parcadei/Continuous-Claude-v3 --skill explore -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install parcadei/Continuous-Claude-v3 explore --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/explore .claude/skills/explore && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
explore
GitHub stars
3.9k
Used in
2 other repos
Token cost
~2.9k tokens
SKILL.md length
522 words
Files
1
Skills in repo
141
Repo updated
First seen
Licence
MIT

At a glance

Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)

  • Works in 5 steps: Workflow Selection → Exploration Goal → Scope → …
  • SKILL.md covers Usage, Question Flow (No Arguments), Examples and Workflow Details, plus 6 more sections
  • Calls uv

What it does

Explore is an agent skill from parcadei/Continuous-Claude-v3. Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows. The licence is MIT.

Example prompts

  • “/explore”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Bash, Task, Read, Glob, Grep, Write

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Workflow Selection
  2. Exploration Goal
  3. Scope
  4. Output Format
  5. Entry Point (Architecture only)

What it can do on your machine

Read from SKILL.md and the folder at commit d07ff4b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Task
    • Read
    • Glob
    • Grep
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Explore loads about 2.9k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 522 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Task, Read, Glob, Grep, Write

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from parcadei/Continuous-Claude-v3 at commit d07ff4b, republished under its MIT licence (© parcadei). 522 words, ~2,884 tokens.

Download SKILL.mdSave it as .claude/skills/explore/SKILL.md (or your agent's skills folder).
name
explore
description
Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)
allowed-tools
Bash, Task, Read, Glob, Grep, Write
keywords
explore, codebase, architecture, understand, analyze, layers, call graph, brownfield

Explore - Internal Codebase Exploration

Meta-skill for exploring an internal codebase at varying depths. READ-ONLY workflow - no code changes.

Usage

/explore <depth> [options]

Question Flow (No Arguments)

If the user types just /explore with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase.

Phase 0: Workflow Selection
yaml
question: "How would you like to explore?"
header: "Explore"
options:
  - label: "Help me choose (Recommended)"
    description: "I'll ask questions to pick the right exploration depth"
  - label: "Quick - fast overview"
    description: "Chain: tldr tree → tldr structure (~1 min)"
  - label: "Deep - comprehensive analysis"
    description: "Chain: onboard → tldr → research → document (~5 min)"
  - label: "Architecture - layers & dependencies"
    description: "Chain: tldr arch → call graph → layer mapping (~3 min)"

Mapping:

  • "Help me choose" → Continue to Phase 1-4 questions
  • "Quick" → Set depth=quick, skip to Phase 2 (scope)
  • "Deep" → Set depth=deep, skip to Phase 2 (scope)
  • "Architecture" → Set depth=architecture, skip to Phase 2 (scope)

If Answer is Unclear (via "Other"):

yaml
question: "I want to understand how deep you want to explore. Did you mean..."
header: "Clarify"
options:
  - label: "Help me choose"
    description: "Not sure - guide me through questions"
  - label: "Quick - fast overview"
    description: "Just want to see what's here"
  - label: "Deep - comprehensive analysis"
    description: "Need thorough understanding"
  - label: "Neither - let me explain differently"
    description: "I'll describe what I need"
Phase 1: Exploration Goal
yaml
question: "What are you trying to understand?"
header: "Goal"
options:
  - label: "Get oriented in the codebase"
    description: "Quick overview of structure"
  - label: "Understand how something works"
    description: "Deep dive into specific area"
  - label: "Map the architecture"
    description: "Layers, dependencies, patterns"
  - label: "Find where something is"
    description: "Locate specific code/functionality"

Mapping:

  • "Get oriented" → quick depth
  • "Understand how" → deep depth
  • "Map architecture" → architecture depth
  • "Find where" → quick with --focus
Phase 2: Scope
yaml
question: "What area should I focus on?"
header: "Focus"
options:
  - label: "Entire codebase"
    description: "Explore everything"
  - label: "Specific directory or module"
    description: "I'll specify the path"
  - label: "Specific concept/feature"
    description: "e.g., 'authentication', 'API routes'"

If "Specific directory" or "Specific concept" → ask follow-up for the path/keyword.

Phase 3: Output Format
yaml
question: "What should I produce?"
header: "Output"
options:
  - label: "Just tell me what you find"
    description: "Interactive summary in chat"
  - label: "Create a documentation file"
    description: "Write to thoughts/shared/docs/"
  - label: "Create handoff for implementation"
    description: "Prepare context for coding agent"

Mapping:

  • "Documentation file" → --output doc
  • "Handoff for implementation" → --output handoff
Phase 4: Entry Point (Architecture only)

If architecture depth selected:

yaml
question: "Where should I start the analysis?"
header: "Entry point"
options:
  - label: "Auto-detect (main, cli, app)"
    description: "Find common entry points"
  - label: "Specific function/file"
    description: "I'll specify the entry point"
Summary Before Execution
Based on your answers, I'll run:

**Depth:** deep
**Focus:** "authentication"
**Output:** handoff
**Path:** src/

Proceed? [Yes / Adjust settings]
Depths
DepthTimeWhat it does
quick~1 mintldr-explorer only - fast structure overview
deep~5 minonboard + tldr-explorer + research-codebase + write doc
architecture~3 mintldr arch + call graph + layer mapping + circular dep detection
Options
OptionDescriptionExample
--focus "area"Focus on specific area--focus "auth", --focus "api"
--output handoffCreate handoff for next agent--output handoff
--output docCreate documentation file--output doc
--entry "func"Start from specific entry point--entry "main", --entry "process_request"

Examples

bash
# Quick structure overview
/explore quick

# Deep exploration focused on auth
/explore deep --focus "auth" --output doc

# Architecture analysis from specific entry
/explore architecture --entry "cli" --output handoff

# Quick focused exploration
/explore quick --focus "hooks"

Workflow Details

Quick Depth

Fast structure overview using tldr-explorer. Best for:

  • Initial orientation
  • Quick questions about structure
  • Finding where things are

Steps:

  1. Run tldr tree for file structure
  2. Run tldr structure for codemaps
  3. If --focus provided, run tldr search for targeted results
  4. Return summary

Commands:

bash
# 1. File tree
tldr tree ${PATH:-src/} --ext .py

# 2. Code structure
tldr structure ${PATH:-src/} --lang python

# 3. Focused search (if --focus provided)
tldr search "${FOCUS}" ${PATH:-src/}
Deep Depth

Comprehensive exploration with documentation output. Best for:

  • First time in a codebase
  • Preparing for major work
  • Creating reference documentation

Steps:

  1. Check if onboarded (look for .claude/cache/tldr/), if not run onboard
  2. Run tldr-explorer for structure
  3. Spawn research-codebase agent for patterns
  4. Write findings to doc or handoff

Subprocess:

# 1. Onboard check
if [ ! -f .claude/cache/tldr/arch.json ]; then
    # Spawn onboard agent
fi

# 2. Structure analysis
tldr structure src/ --lang python
tldr calls src/

# 3. Research patterns (via scout agent)
Task: research-codebase → "Document existing patterns in ${FOCUS:-codebase}"

# 4. Write output
→ thoughts/shared/research/YYYY-MM-DD-explore-{focus}.md
→ OR thoughts/shared/handoffs/{session}/explore-{focus}.yaml
Show full SKILL.md (194 more words)Show less
Architecture Depth

Architecture-focused analysis with layer detection. Best for:

  • Understanding system boundaries
  • Preparing for refactoring
  • Identifying coupling issues

Steps:

  1. Run tldr arch for layer detection
  2. Run tldr calls for cross-file call graph
  3. Analyze entry/middle/leaf layers
  4. Detect circular dependencies
  5. Map architectural boundaries

Commands:

bash
# 1. Architecture detection
tldr arch ${PATH:-src/}
# Returns: entry_layer, middle_layer, leaf_layer, circular_deps

# 2. Call graph
tldr calls ${PATH:-src/}
# Returns: edges, nodes

# 3. Impact analysis from entry point (if --entry provided)
tldr impact ${ENTRY} ${PATH:-src/} --depth 3

Output Structure:

yaml
layers:
  entry: [routes.py, cli.py, main.py]  # Controllers/handlers
  middle: [services.py, auth.py]        # Business logic
  leaf: [utils.py, helpers.py]          # Utilities

call_graph:
  total_edges: 142
  hot_paths: [process_request → validate → authorize]

circular_deps:
  - [module_a, module_b]  # A imports B, B imports A

boundaries:
  - name: API layer
    files: [src/api/*]
    calls_to: [src/services/*]

Output Formats

--output doc

Creates: thoughts/shared/research/YYYY-MM-DD-explore-{focus}.md

markdown
---
date: {ISO timestamp}
type: exploration
depth: {quick|deep|architecture}
focus: {focus area or "full"}
commit: {git hash}
---

# Codebase Exploration: {focus}

## Summary
{High-level findings}

## Structure
{File tree / codemaps}

## Architecture
{Layer analysis - for architecture depth}

## Key Components
{Important files and their roles}

## Patterns Found
{Existing patterns - for deep depth}

## References
- `path/to/file.py:line` - Description
--output handoff

Creates: thoughts/shared/handoffs/{session}/explore-{focus}.yaml

yaml
---
type: exploration
ts: {ISO timestamp}
depth: {quick|deep|architecture}
focus: {focus area}
commit: {git hash}
---

summary: {One-line summary of findings}

structure:
  entry_points: [{main.py}, {cli.py}]
  key_modules: [{auth.py}, {routes.py}]
  test_coverage: [{tests/}]

architecture:
  layers:
    entry: [{files}]
    middle: [{files}]
    leaf: [{files}]
  circular_deps: [{pairs}]

findings:
  - {key finding with file:line}

next_steps:
  - {Recommended action based on exploration}

refs:
  - path: {file.py}
    role: {what it does}

Integration with /build

The explore skill is designed to feed into /build brownfield:

bash
# Step 1: Explore to understand
/explore architecture --output handoff

# Step 2: Build with context from exploration
/build brownfield --from-handoff thoughts/shared/handoffs/session/explore-full.yaml

Implementation

When user invokes /explore <depth> [options]:

Parse Arguments
python
depth = args[0]  # quick | deep | architecture
focus = extract_option(args, "--focus")
output = extract_option(args, "--output")  # handoff | doc
entry = extract_option(args, "--entry")
Execute Based on Depth

Quick:

bash
# Just tldr commands, no agents
tldr tree ${src_dir} --ext .py
tldr structure ${src_dir} --lang python
if [ -n "$focus" ]; then
    tldr search "$focus" ${src_dir}
fi

Deep:

bash
# 1. Check/run onboard
if [ ! -f .claude/cache/tldr/meta.json ]; then
    # Spawn onboard agent via Task tool
fi

# 2. Structure
tldr structure src/ --lang python

# 3. Research (spawn scout agent)
# Task tool with subagent_type: "scout"
# Prompt: "Research patterns in ${focus:-codebase}"

# 4. Write output
# → doc or handoff based on --output

Architecture:

bash
# 1. Arch detection
arch_output=$(tldr arch ${src_dir})

# 2. Call graph
calls_output=$(tldr calls ${src_dir})

# 3. Impact from entry (if provided)
if [ -n "$entry" ]; then
    impact_output=$(tldr impact $entry ${src_dir} --depth 3)
fi

# 4. Synthesize and write output

Key Principles

  1. READ-ONLY - This skill never modifies code
  2. Uses scout, not Explore - Per project rules, scout (Sonnet) over Explore (Haiku)
  3. Token-efficient - Uses tldr commands (95% savings over raw reads)
  4. Outputs to shared locations - thoughts/shared/research/ or handoff directory
  5. Entry point to /build - Exploration handoffs feed into brownfield builds
SkillWhen to Use
tldr-explorerDirect tldr commands (used internally by explore)
tldr-codeSpecific analysis commands (cfg, dfg, slice)
onboardFirst-time project setup (used by deep depth)
research-codebasePattern documentation (used by deep depth)
create_handoffHandoff format (used by --output handoff)

Troubleshooting

tldr not found:

bash
# Check if installed
which tldr
# Install if missing
uv tool install llm-tldr
# or: pip install llm-tldr

No Python files found:

bash
# Check language, adjust --lang
tldr structure src/ --lang typescript  # or go, rust

Empty architecture output:

bash
# May need to specify src directory
tldr arch ./  # Current directory
tldr arch src/  # Explicit src

© parcadei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/explore of parcadei/Continuous-Claude-v3.

Open the folder on GitHubat commit d07ff4b

Used in 2 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in parcadei/Continuous-Claude-v3, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Explore next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Explore compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Explore this skillparcadei/Continuous-Claude-v33.9k2 repos~2.9kAutomated safety check: NotesMIT
Internal Commsalirezarezvani/claude-skills28k—~3.4kAutomated safety check: PassMIT
Internal Communicationsickn33/agentic-awesome-skills47k1 repos~3.4kAutomated safety check: PassMIT
Internal Communications Writeranthropics/skills180k37 repos~378Automated safety check: PassApache-2.0
Internal Comms Anthropicsickn33/agentic-awesome-skills47k1 repos~702Automated safety check: PassApache-2.0
Agent Scout Explorerruvnet/ruflo74k3 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Internal Comms

    alirezarezvani/claude-skills

    A skill your agent uses when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement…

    28k GitHub stars~3.4k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Internal Communication

    sickn33/agentic-awesome-skills

    Internal communication log: title, type, date, department, host and attendees, agenda, action items, follow-up date, meeting link and delivery status.

    47k GitHub starsUsed in 1 repo~3.4k tokens
    Writing & ContentAuto-check passed

  • Internal Communications Writer

    anthropics/skills

    Official

    A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…

    180k GitHub starsUsed in 37 repos~378 tokens
    Writing & ContentAuto-check passed

  • Internal Comms Anthropic

    sickn33/agentic-awesome-skills

    Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources.

    47k GitHub starsUsed in 1 repo~702 tokens
    Writing & ContentAuto-check passed

  • Agent Scout Explorer

    ruvnet/ruflo

    Agent skill for scout-explorer - invoke with $agent-scout-explorer

    74k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed

  • Nofollow Internal

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing internal link structure or reviewing link attributes.

    74k GitHub stars~579 tokensUpdated yesterday
    Auto-check passed

More from parcadei/Continuous-Claude-v3

All 141 skills in this repo

  • Tldr Deep

    parcadei/Continuous-Claude-v3

    Full 5-layer analysis of a specific function. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 2 repos~677 tokens
    Auto-check passed

  • Compound Learnings

    parcadei/Continuous-Claude-v3

    Transform session learnings into permanent capabilities (skills, rules, agents).

    3.9k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check: notes

  • Gradient Methods

    parcadei/Continuous-Claude-v3

    Problem-solving strategies for gradient methods in optimization

    3.9k GitHub starsUsed in 3 repos~1k tokens
    Auto-check: notes

  • Debug Hooks

    parcadei/Continuous-Claude-v3

    Systematic hook debugging workflow. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 1 repo~863 tokens
    Auto-check: notes

  • Math

    parcadei/Continuous-Claude-v3

    Unified math capabilities - computation, solving, and explanation.

    3.9k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check: notes

  • Math Model Selector

    parcadei/Continuous-Claude-v3

    Routes problems to appropriate mathematical frameworks using expert heuristics

    3.9k GitHub starsUsed in 3 repos~841 tokens
    Auto-check passed

Questions about Explore

What does Explore do?

Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture). Explore is an agent skill from parcadei/Continuous-Claude-v3.

How do I install Explore in Claude Code?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill explore -a claude-code`. Or copy the skill folder (.claude/skills/explore in parcadei/Continuous-Claude-v3) into .claude/skills/explore in your project. Claude Code loads it when a task matches its description.

How do I install Explore in Codex?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill explore -a codex`. Or copy the skill folder (.claude/skills/explore in parcadei/Continuous-Claude-v3) into .agents/skills/explore in your project. Codex loads it when a task matches its description.

Can I use Explore in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add parcadei/Continuous-Claude-v3 --skill explore -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explore, .gemini/skills/explore, .github/skills/explore and .opencode/skills/explore in your project.

What does Explore need to run?

Going by SKILL.md and its folder, Explore needs the command-line tools its instructions call (uv). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Task, Read, Glob, Grep, Write.

Does Explore access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Explore safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Explore use?

Explore is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Explore use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Explore?

Skills that share tags, products or a category with Explore: Internal Comms (alirezarezvani/claude-skills, 28k stars), Internal Communication (sickn33/agentic-awesome-skills, 47k stars), Internal Communications Writer (anthropics/skills, 180k stars) and Internal Comms Anthropic (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Explore?

parcadei (a GitHub user) maintains it in parcadei/Continuous-Claude-v3, which has 3,940 GitHub stars. The repository holds 141 skills in this directory. The repository was last updated on January 26, 2026.

Source: parcadei/Continuous-Claude-v3 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.