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 trigger terms that would help Claude select it accurately from a large skill set.
| 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 strong skill with excellent actionability through concrete JSON examples and well-structured multi-step workflows with error handling. The anti-patterns table is a particularly effective format for quick reference. Minor verbosity in the troubleshooting section and some explanatory text could be tightened, but overall the content is well-organized and practical.
Suggestions
Tighten the troubleshooting section by using a more concise format (e.g., bold problem + single-line solution) instead of full paragraph explanations for each scenario.
| 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 is somewhat verbose with full sentences restating things Claude would infer). The anti-patterns table is well-structured but some entries explain obvious things. | 2 / 3 |
Actionability | Provides concrete JSON examples for every message type, specific file paths for teammate discovery, and exact field names/values. The plan approval workflow and shutdown protocol include copy-paste ready JSON payloads with realistic field values. | 3 / 3 |
Workflow Clarity | Multi-step processes (plan approval, shutdown protocol) are clearly sequenced with numbered steps and explicit handling of failure cases (rejection handling, retry logic). The shutdown protocol includes a feedback loop for handling rejections before proceeding. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections with clear headers. Related skills are linked at the bottom for deeper exploration. The skill is appropriately self-contained for its scope without being monolithic, and references to related skills are one level deep. | 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
91fe43e
- 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.