Meta-skill: how to pass skills/context to Claude sub-agents that start with fresh context, with documented SDK gotchas.
94
94%
Does it follow best practices?
Impact
96%
1.50xAverage score across 3 eval scenarios
Passed
No known issues
The main SKILL.md calls out the single most dangerous gotcha (the context: fork
semantic inversion). The issues below are additional papercuts and documentation bugs
that a sub-agent orchestrator should be aware of.
context: fork is semantically invertedfork creates an ISOLATED blank context, not a copy of the parent. If you rely on
the English meaning you will ship a broken orchestrator.
AskUserQuestion is silently unavailable in sub-agentsThe tool is listed as available but calls fail or return empty. Sub-agents that rely on human-in-the-loop clarification will freeze or loop.
If you do not pin model in the AgentDefinition, the sub-agent may run on a
different (often weaker) model. Symptoms look like a capability regression that turns
out to be a routing regression.
Sub-agents can currently pick up skills directly from .claude/skills/ on disk, but
the documentation says they can't. This works today, may break tomorrow, and should
not be used as a production channel for passing skills.
17 upvotes as of writing. Until this lands, every sub-agent starts fully blank except
for CLAUDE.md, tools, and MCP servers — which is the premise of this whole skill.
Some sub-agent invocations have been observed routing through higher-priced models without warning, producing unexpectedly large bills.
These references back the core SKILL.md. If you close any of the above tracking
issues with resolutions that change the inheritance model, also update the skill body
so future orchestrators don't act on stale assumptions.