AugmentClaude

Agent Exploration

Research multiple topics in parallel and synthesize findings into evidence-backed reports.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/agent-exploration-compozy/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Works for every skill.

    What this command does
    1. Makes a new, empty temporary folder.
    2. Downloads the skill's folder, .agents/skills/agent-exploration, from github.com/compozy/compozy (branch main), the GitHub repository it's listed from. You get the version that is there now, not a copy we keep.
    3. Copies that folder to ~/.claude/skills/agent-exploration-compozy/.
    4. Deletes the temporary folder.

    Installing runs none of the skill's files; it only downloads and copies them. When you later use the skill, Claude follows its SKILL.md and may run scripts that come with it. Read them first.

    How we check skills, and what we don't · Report this skill

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Coordinate native explorers for explicitly requested multi-area research with scoped written results and an evidence-backed synthesis.

What this skill does

Agent Exploration

Use when explicitly requested for research across independent areas with written results. Use the current harness's native explorers and configured model/effort; an explicit user override wins. Do not invoke an external runtime or create an agent registry for this workflow.

Scope and dispatch

  1. Resolve the question and output path from the request or active task. Ask only for genuinely missing scope; creating the requested directory needs no additional confirmation. Default an unspecified artifact location to .audits/exploration/<timestamp>/ and state it.
  2. Reuse current grounding. Scout only enough to identify independent questions; no tool-call or source-count quota. Choose as many useful slices as capacity and scope justify, up to 8; --agents is an upper bound, not a target to pad.
  3. Read references/dispatch-rules.md and assets/explorer-prompt.md once when preparing dispatch. Send each explorer its question, source scope, exact output path, and the scoped-write contract once. Include assets/analysis-template.md when a structured artifact is needed; do not duplicate the contract in several embedded documents.
  4. Create the output directory, then dispatch independent slices as capacity permits. Prompts need durable copies only for a long/resumable run. Every worker is read-only except for its named analysis file; no commits or unrelated edits.
  5. Inspect each completed artifact and its material citations. A failed slice does not invalidate successful siblings. Continue or correct the affected worker; do not launch a fresh whole round for a missing heading or confirmation sentence.
  6. Write analysis/summary.md with the answer, evidence links, disagreements, remaining gaps, and actionable conclusions. Distinguish completed and unavailable slices; never claim an unperformed investigation succeeded.

Use analysis/NN_analysis_<slug>.md for each slice. Preserve externally required schemas; otherwise keep sections as short as their evidence permits. references/checklist.md is an inspection aid, not an extra approval stage. Routine single-file lookups need no delegation or research artifact.

Related skills