team-communication-protocols
Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing communication norms for a newly spawned team, when deciding whether to send a direct message or a broadcast, when a team-lead needs to review and approve an implementer's plan before work begins, when orchestrating a graceful team shutdown after all tasks are complete, or when debugging why teammates are not coordinating correctly at integration points.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its domain (agent team communication protocols), lists specific capabilities, and provides an extensive 'Use this skill when...' clause with five distinct trigger scenarios. The description is well-structured, uses third person voice appropriately, and includes natural keywords that would help Claude select it in the right contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. These are clearly defined capabilities within the domain of agent team communication. | 3 / 3 |
Completeness | Clearly answers both 'what' (structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, anti-patterns) and 'when' with an explicit 'Use this skill when...' clause listing five distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'communication norms', 'direct message', 'broadcast', 'plan approval', 'team shutdown', 'coordinating', 'integration points', 'spawned team', 'team-lead', 'implementer'. Good coverage of terms relevant to multi-agent orchestration scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche around agent-to-agent communication protocols and team coordination. The specific focus on messaging protocols, plan approval workflows, and shutdown procedures makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability through concrete JSON examples and clear multi-step workflows with validation checkpoints. The anti-patterns table is a valuable addition. The main weakness is moderate verbosity in the troubleshooting section, which largely restates guidance already present in earlier sections, and some explanatory text that Claude wouldn't need (e.g., explaining why broadcasts are expensive).
Suggestions
Trim the troubleshooting section — most entries restate information from the main sections (e.g., broadcast anti-pattern, shutdown rejection handling). Consider condensing to a brief FAQ or removing entirely.
Remove explanatory asides like 'Why sparingly?' that explain concepts Claude can infer from the anti-patterns table and the concrete guidance already provided.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., 'Why sparingly?' explanation about API resources, the troubleshooting section restates information already covered in the anti-patterns and shutdown sections). The anti-patterns table is well-structured but some entries overlap with detailed sections. The troubleshooting section adds bulk by re-explaining concepts already covered. | 2 / 3 |
Actionability | Provides concrete JSON examples for every message type, specific file paths for teammate discovery, and exact field names/values for plan approval and shutdown responses. All examples are copy-paste ready with realistic payloads. | 3 / 3 |
Workflow Clarity | Both the plan approval workflow and shutdown protocol have clearly numbered sequences with explicit validation/feedback loops (reject with feedback, handle rejections, retry). The shutdown protocol includes error recovery steps for rejections and a clear terminal condition (TeamDelete after all teammates shut down). | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections with clear headers. Related skills are linked at the bottom with one-level-deep references and brief descriptions of when to use them. The skill is appropriately self-contained without being monolithic. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
27a7ed9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.