agentleFS
ryanmacleanryanmaclean/skills/delegate/SKILL.md

delegate

Skill1 starsChanged 50 days agoMITView on GitHub

Use when the user says "ask an agent to", "create a team to", "IRC task to", "check with <host>", "have the fleet", "spawn", or "delegate" — signals work should be routed to a subagent, fleet bot, or specific node rather than done inline.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use state, preview and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    state

    Store and query a Microsoft Managed App's built-in state and file attachments with `ms project state` CLI schema commands and generated TypeScript clients. First, with the user signed in to the CLI, run `ms feature status --name state --json`; if `feature.enabled` is not `true`, recommend an alternative connector or data source.

    Also in 3 projects that use this

  • kv0906Skill

    preview

    Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 5 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    skill-authoring

    Write Agent Skills that comply with the agentskills.io specification. WHEN: "create a skill", "new skill", "write a skill", "skill template", "skill structure", "review skill", "skill PR", "skill compliance", "SKILL.md format", "skill frontmatter", "skill best practices". DO NOT USE FOR: general documentation. INVOKES: vally CLI.

    Also in 3 projects that use this

The file

Files
SKILL.md

Delegate — Routing Work to the Right Executor

Trigger Phrases → Action

User saysWhat to do
"Ask an agent to <task>"Spawn a single background agent via Task tool
"Create a team to <task>"Spawn parallel agents via zellij-team or tiger-team skill
"IRC task to <task>"Post to #agents on IRC — fleet self-assigns
"Check with <host> about <thing>"SSH/Ansible query, or DM the bot via IRC
"Have the fleet <task>"IRC broadcast to #agents
"Ask ubrpi502 to <task>"DM specific bot via IRC or SSH directly
"Spawn" / "Delegate"Route to appropriate method below

Method 1: Task Tool (single agent)

"Ask an agent to find all Rust files with async/await"
→ Agent tool, focused prompt, run_in_background: true if independent

Subagent types: Explore (search/find), general-purpose (research/multi-step), Plan (architecture)

GSD subagents: gsd-phase-researcher, gsd-planner, gsd-executor, gsd-debugger, gsd-verifier

Method 2: Agent Teams (parallel)

"Create a team to review the auth module"
→ zellij-team skill  — independent parallel tasks
→ tiger-team skill   — one hard problem, multiple expert lenses (attacker/defender/architect/pragmatist)

Method 3: IRC Fleet Dispatch

"IRC task to check disk space on all Pis"
→ Post to #agents via i9 zeroclaw (connected to IRC at 10.0.3.203:6697)

IRC message format:

  • all: <task> or fleet: <task> — every bot responds
  • ubrpi502: <task> — only that bot responds

Send from Claude Code:

ssh studio@10.0.2.230 "zeroclaw channel send '#agents' 'fleet: <task>'"
ssh studio@10.0.2.230 "zeroclaw channel send 'ubrpi401' 'ubrpi401: <task>'"

Method 4: SSH / Ansible (specific node)

"Check with ubrpi502 about build status"
→ ansible ubrpi502 -i ansible/inventory -m raw -a "<command>"
→ ssh ubuntu@<ip> "<command>"

Long-running work: use Zellij on the node (ssh node → zellij attach research → claude)

Web access: http://<node-ip>:7681 (ttyd, port 7681 on all fleet nodes)

Decision Table

SituationMethod
Quick code searchTask (Explore)
Multi-step researchTask (general-purpose)
Multiple independent problemszellij-team
One hard problem, need multiple anglestiger-team
Fleet-wide survey / self-organizingIRC #agents
Specific node querySSH / Ansible
Long-running agent sessionZellij + SSH

Key Fleet Nodes

NodeIPRole
ubrpi50210.0.3.193Best Pi build node (Pi 5, 16GB)
pop4090 / 7950x4090pop10.0.2.42Heavy LLM, gastown coordinator
i9-zfs-pop10.0.2.230Gitea, IRC gateway, gastown coordinator
#agents IRC10.0.3.203:6697Fleet-wide broadcast

Verification contract

Routing work through this skill spawns sub-agents (Task tool, zellij-team, tiger-team, IRC fleet bots, etc.). Every sub-agent dispatched by this skill MUST attach a proveryay claims block to its final report so the parent can verify instead of trust.

Reference: ~/.claude/skills/proveryay/CLAIMS-TEMPLATE.md (YAML-under-XML is the canonical format; atomic JSON is also accepted).

Example appropriate to delegation work (the sub-agent ran a fleet task and is reporting back):

<claims>
- claim: "Task completed on ubrpi502"
  probe: "ansible ubrpi502 -i ansible/inventory -m raw -a 'test -f /tmp/delegate-done'"
  expect: "SUCCESS"
- claim: "IRC dispatch received by #agents"
  probe: "tail -5 ~/irc/10.0.3.203/#agents/out | grep -c '<task-id>'"
  expect: "1"
- claim: "Sub-agent produced expected artifact"
  probe: "ls -l /Users/studio/rust-town/out/<task-id>.json"
  expect: ".json"
- claim: "Remote service reachable after change"
  probe: "curl -sS -m 5 -o /dev/null -w '%{http_code}' http://gitea.local:3000/api/v1/version"
  expect: "200"
- claim: "No other fleet host degraded"
  probe: "ansible linux_pis_reachable -i ansible/inventory -m ping -o | grep -c SUCCESS"
  expect: "7"
</claims>

Sub-agents spawned by this skill MUST emit this block in their final report. proveryay (SubagentStop hook) will verify each probe in parallel and inject verdicts into the parent agent's next turn — claims without the block are taken on faith and are therefore rejected by the AX-first discipline.

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.