agentleFS
yeisonrestrepoyeisonrestrepo/code-conductor/skills/agent-delegation/SKILL.md

agent-delegation

Skill17 starsChanged 37 days agoMITView on GitHub

Rules for when and how to spawn sub-agents: Explore for 3+ file reads, parallel agents for independent tasks, summaries only — raw output never enters main context

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. kangarooking/system-prompt-skills★ 178same name
    2. shaokeyibb/agent-delegation★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the main context clean.

    line 9
  2. Distinctive:

    Every sub-agent returns ≤200 words to the main context.

    line 37
  3. Distinctive:

    If a sub-agent needs user input, it surfaces one question to the main context and stops.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Delegation

Keep the main context clean. Raw file contents, grep output, and intermediate data never enter the main context. Sub-agents process data and return summaries only.

When to Spawn

Explore Sub-Agent

Condition: Task requires reading 3+ files to answer one question, or codebase exploration precedes implementation.

// Use the Agent tool with these parameters:
Agent({
  subagent_type: "Explore",
  description: "<10-word description of the lookup>",
  prompt: "<question>. Search across relevant files. Return a summary of ≤200 words. Do not include raw file contents."
})

Parallel Agents

Condition: 2+ implementation tasks with no shared state, each describable independently.

Send both Agent calls in a single message so they run in parallel:

// Use the Agent tool twice in the same message — they run in parallel:
Agent({ description: "Task A", prompt: "... Return a summary of ≤200 words." })
Agent({ description: "Task B", prompt: "... Return a summary of ≤200 words." })

Output Contract

  • Every sub-agent returns ≤200 words to the main context.
  • The main context acts only on summaries, not raw data.
  • If a sub-agent needs user input, it surfaces one question to the main context and stops.

When NOT to Spawn

  • Single Grep or Glob can answer the question.
  • Answer is already in .claude/memory/project.md.
  • Task requires back-and-forth with the user (stay inline).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.