Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When spawning a new agent team, deciding direct message vs broadcast, requiring lead plan approval before implementation, orchestrating graceful shutdown, or debugging coordination failures at integration points.
message (direct), broadcast (sparing), shutdown_requestExitPlanMode → plan_approval_responseClear communication norms: correct message routing, approved plans before work, clean team teardown, and resolved coordination deadlocks.
Use Cases
A user spawns a 4-agent team to build a feature. The lead uses this skill to set norms: direct messages for integration notices, broadcast only for shared-type changes, and plan_mode approval before coding. Result: no resource waste, plans reviewed, teammates coordinate at interfaces without deadlock.
After tasks finish, the lead triggers graceful shutdown: sends shutdown_request to each, handles a rejection by waiting, then TeamDelete. Using the protocol avoids force-killing teammates with unsaved work and keeps state safe. The skill's troubleshooting fixes a deadlock where two implementers waited on each other.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File