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
Security Assessment
About team-communication-protocols
The 'team-communication-protocols' skill provides a set of protocols designed to optimize communication within a team of agents, addressing common coordination issues and ensuring streamlined communication across various stages of teamwork. It focuses on the selection of appropriate message types, establishing plan approval workflows, managing team shutdowns, and identifying communication anti-patterns to avoid. This skill is crucial for teams that require efficient communication norms, particularly in complex, multi-agent environments where coordination can become difficult as tasks progress or when integration points are reached.
FAQ
When should I use this skill?
This skill should be used when establishing communication norms for new teams, selecting message types, handling plan approvals, managing team shutdowns, or debugging communication issues between teammates.
What message types are available in this skill?
The skill provides three primary message types: 'message' (direct message), 'broadcast' (for communication with all teammates), and 'shutdown_request' (for requesting team shutdowns).
Are there any limitations to the message types?
Yes, broadcasts should be used sparingly as they consume significant API resources, especially with larger teams. Sending routine updates via broadcast or using JSON status messages is considered an anti-pattern.
What is the plan approval workflow?
The plan approval workflow involves a teammate submitting a plan, which is then reviewed and either approved or rejected by a team lead. If rejected, feedback is provided for revisions.
What anti-patterns should be avoided?
Key anti-patterns include broadcasting routine updates, micromanaging via messages, ignoring idle teammates, and using UUIDs instead of teammate names. These practices can hinder communication and productivity.
Install team-communication-protocols
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
wshobson/agents