Agent skill

Compose

by sharpdeveye in sharpdeveye/maestro

A skill your agent uses when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

MITAuto-check passedAgent Workflows

Install Compose

skills CLI
$ npx skills add sharpdeveye/maestro --skill compose -a claude-code

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

GitHub CLI
$ gh skill install sharpdeveye/maestro compose --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/sharpdeveye/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/source/skills/compose .claude/skills/compose && 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
compose
GitHub stars
592
Token cost
~720 tokens
SKILL.md length
292 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

  • Works in 4 steps: Pre-Composition Check → Design the Topology → Design Handoffs → …
  • A single agent demonstrably cannot handle the task and multi-agent coordination is justified
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Multi-agent orchestration

What it does

Compose is an agent skill from sharpdeveye/maestro. Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

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

It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and… The licence is MIT.

When your agent uses it

  • A single agent demonstrably cannot handle the task and multi-agent coordination is justified
  • Tasks that involve Multi-agent orchestration

Example prompts

  • “/compose”

Workflow steps

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

  1. Pre-Composition Check
  2. Design the Topology
  3. Design Handoffs
  4. Design the Supervisor

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

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

  • Network

    No URLs in SKILL.md.

    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

Compose loads about 720 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 292 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 sharpdeveye/maestro at commit 00f9115, republished under its MIT licence (© sharpdeveye). 292 words, ~720 tokens.

Download SKILL.mdSave it as .claude/skills/compose/SKILL.md (or your agent's skills folder).
name
compose
description
Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.
argument-hint
[workflow description]
category
enhancement
version
2.0.0
user-invocable
true

MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first. Consult the agent-architecture reference in the agent-workflow skill for topology patterns and when multi-agent is justified.


Design a multi-agent system. But first — are you sure you need one?

Step 1: Pre-Composition Check

Answer these before proceeding:

  1. Has a single agent been tried and failed? (If no, try single agent first)
  2. What specific limitation requires multiple agents? (If you can't name it, you don't need multi-agent)
  3. Is the cost/latency increase justified? (Multi-agent = 2-10x cost and latency)

If you can't articulate a specific limitation, use /amplify on the single agent instead.

Step 2: Design the Topology

Choose the right architecture pattern (consult the agent-architecture reference in the agent-workflow skill):

For each agent in the system, define:

markdown
## Agent: [Name]
Role: [One sentence]
Responsibilities: [What it does]
Boundaries: [What it does NOT do]
Tools: [List of tools this agent has access to]
Input: [What it receives]
Output: [What it produces]
Step 3: Design Handoffs

For each agent-to-agent connection:

markdown
## Handoff: [Agent A] → [Agent B]
Trigger: [When does A hand off to B?]
Payload: [What data is passed?]
Expected response: [What does A expect back?]
Timeout: [How long to wait?]
Failure handling: [What if B fails?]
Step 4: Design the Supervisor

Every multi-agent system needs a supervisor:

  • Monitors agent health and performance
  • Routes tasks to appropriate agents
  • Handles failures and escalation
  • Enforces global constraints (budget, time, quality)
Composition Checklist
  • Each agent has a clear, non-overlapping role
  • Handoff protocols are defined for every connection
  • A supervisor pattern is in place
  • Cost/latency budget accounts for all agents
  • Failure modes are handled at every handoff point
  • The system can be understood by reading the topology diagram

After composition, run /fortify to add error handling at every handoff, then /evaluate to test the multi-agent system end-to-end.

NEVER:

  • Build multi-agent for a problem a single agent can handle
  • Create agents with overlapping responsibilities
  • Skip the supervisor (autonomous swarms are unpredictable)
  • Pass full context between all agents (pass only what's needed)
  • Compose without defining handoff protocols

© sharpdeveye, 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 source/skills/compose of sharpdeveye/maestro.

Open the folder on GitHubat commit 00f9115

Compare with similar skills

Compose 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.

Compose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Compose this skillsharpdeveye/maestro592—~720Automated safety check: PassMIT
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Mission Control Agent APIbuilderz-labs/mission-control6.3k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed
  • Mission Control Agent API

    builderz-labs/mission-control

    Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.

    6.3k GitHub stars~2.1k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

More from sharpdeveye/maestro

All 25 skills in this repo
  • Accelerate

    sharpdeveye/maestro

    A skill your agent uses when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.

    592 GitHub stars~745 tokensUpdated 5 mo ago
    Auto-check passed
  • Chain

    sharpdeveye/maestro

    A skill your agent uses when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.

    592 GitHub stars~607 tokensUpdated 5 mo ago
    Auto-check passed
  • Diagnose

    sharpdeveye/maestro

    A skill your agent uses when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.

    592 GitHub stars~1.5k tokensUpdated 5 mo ago
    Auto-check passed
  • Extract Pattern

    sharpdeveye/maestro

    A skill your agent uses when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

    592 GitHub stars~664 tokensUpdated 5 mo ago
    Auto-check passed
  • Fortify

    sharpdeveye/maestro

    A skill your agent uses when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.

    592 GitHub stars~688 tokensUpdated 5 mo ago
    Auto-check passed
  • Guard

    sharpdeveye/maestro

    A skill your agent uses when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.

    592 GitHub stars~783 tokensUpdated 5 mo ago
    Auto-check passed

Categories

Questions about Compose

What does Compose do?

A skill your agent uses when a single agent demonstrably cannot handle the task and multi-agent coordination is justified. Compose is an agent skill from sharpdeveye/maestro. Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

When should I use Compose?

Compose fits situations like: A single agent demonstrably cannot handle the task and multi-agent coordination is justified; tasks that involve Multi-agent orchestration.

How do I install Compose in Claude Code?

Run `npx skills add sharpdeveye/maestro --skill compose -a claude-code`. Or copy the skill folder (source/skills/compose in sharpdeveye/maestro) into .claude/skills/compose in your project. Claude Code loads it when a task matches its description.

How do I install Compose in Codex?

Run `npx skills add sharpdeveye/maestro --skill compose -a codex`. Or copy the skill folder (source/skills/compose in sharpdeveye/maestro) into .agents/skills/compose in your project. Codex loads it when a task matches its description.

Can I use Compose 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 sharpdeveye/maestro --skill compose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/compose, .gemini/skills/compose, .github/skills/compose and .opencode/skills/compose in your project.

What does Compose need to run?

SKILL.md names no scripts, command-line tools or credentials: Compose is instructions for the agent only.

Does Compose access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Compose safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Compose use?

Compose 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 Compose use?

About 720 tokens (SKILL.md is roughly 2.9k 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 Compose?

Skills that share tags, products or a category with Compose: Orca CLI (stablyai/orca, 87k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Compose?

sharpdeveye (a GitHub user) maintains it in sharpdeveye/maestro, which has 592 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on April 29, 2026.

Source: sharpdeveye/maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.