Subagent broker
Ten Claude Code skills that fix bugs Anthropic closed as 'not planned'.
npx -y skills add dhruba-datta/claude-papercuts --skill subagent-brokerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Battle-tested Task-tool delegation templates that survive the subagent-delegation pitfalls reported in issues #4182, #5528, and #19077. Use this skill when the user runs /claude-papercuts:subagent-broker, asks how to delegate work to subagents reliably, asks when to use the Task tool, says their subagents ignore configuration or CRITICAL directives, or wants a template for parallel search / independent review / cross-file audit. Runs templates.py to list named delegation patterns and prints the one matching the user's situation.
SKILL.md
5.1 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
subagent-broker — Task-tool delegation patterns that actually work
What this prevents
"Sub-agents claim no Task tool access despite configuration stating tools: Read, Write, Edit, Task. CRITICAL rules are completely disregarded. No actual delegation occurs." — issue #5528
"Sub-Agent Task tool not exposed when launching nested agents." — issue #4182
The Task tool is the official delegation mechanism, but it fails silently when the delegation prompt isn't structured right:
- Open-ended prompts return shallow output
- "CRITICAL" / "ALWAYS" directives are ignored
- Briefed-with-conclusion prompts produce sycophantic "yes" answers
- Subagent results aren't shared between subagents (people assume they are)
subagent-broker ships the prompt skeletons that survive these
pitfalls — distilled from the issue threads themselves.
The templates
| Template | When to use |
|---|---|
parallel-search | N independent searches at once (call all Task tools in one message) |
single-research | One open-ended exploration noisy in the main context |
cross-file-audit | Consistency review across files (front-load + re-assert the rule) |
known-target | Don't delegate — use Read/Grep directly |
independent-verification | Second opinion without anchoring on your conclusion |
How to invoke (the actual procedure)
-
Run the templates script to see what's available:
${CLAUDE_PLUGIN_ROOT}/skills/subagent-broker/templates.py -
Ask the user which delegation flavor matches their task:
- Parallel search across the codebase →
parallel-search - One deep research question →
single-research - Cross-file consistency check →
cross-file-audit - "I know exactly which file I need" →
known-target(don't delegate) - Second opinion / independent review →
independent-verification
- Parallel search across the codebase →
-
Print the chosen template:
${CLAUDE_PLUGIN_ROOT}/skills/subagent-broker/templates.py <name> -
Adapt the placeholders (
<files>,<specific concern>, etc.) to the user's actual task. Then make the Task call yourself. -
Never invoke
Taskblindly. The user should see the proposed delegation prompt and approve it before you fire.
The non-obvious rules (from the issues)
- State the most-important constraint twice. Once near the top of
the prompt, once in the response-format section.
CRITICAL/ALWAYSkeywords don't help; placement does. (issue #5528) - Cap the response length explicitly. Subagents will read every file they find if you don't tell them not to.
- Parallelize in a single message. Two
Taskcalls in two consecutive messages run sequentially. TwoTaskcalls in the same message run in parallel. - Don't tell the subagent your conclusion. They'll anchor on it. For verification, withhold your analysis.
- Subagents are 5-10× more expensive than a direct tool call. Delegate only when the subagent will make 3+ tool calls.
When to auto-invoke
- User runs
/claude-papercuts:subagent-broker - User asks how to use Task / subagents / delegation
- User says subagents ignore their config / CRITICAL rules
- User wants a template for parallel work / cross-file review
What this skill does NOT do
- It does not fire the Task tool for you. You (Claude) call Task yourself with the adapted template — the user reviews the prompt first.
- It does not validate that your delegation succeeded. The subagent's own output is the verdict.
- It is not a queue / dispatcher. Earlier drafts of this skill shipped a queue + spawn system; we cut it because it duplicates what Anthropic's Task tool already does.
Configuration
# List every template
${CLAUDE_PLUGIN_ROOT}/skills/subagent-broker/templates.py
# Print one ready to paste
${CLAUDE_PLUGIN_ROOT}/skills/subagent-broker/templates.py parallel-search
# Filter by keyword
${CLAUDE_PLUGIN_ROOT}/skills/subagent-broker/templates.py --search research
# Machine-readable
${CLAUDE_PLUGIN_ROOT}/skills/subagent-broker/templates.py --json
Deprecation plan
If Anthropic ships first-class delegation reliability (per issues #4182, #5528, #19077), the templates become less load-bearing and this skill can simplify or deprecate.