Agent skill · operations · borghei
team-communications
Design a delivery team's communication system — channel routing, meeting-load reduction, status structure, escalation SLAs, timezone norms. Use when the calendar is full, updates go unread, or blockers surface late.
Why this skill is useful
Provides a structured approach to optimize team communication and meeting efficiency, which the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Team Communications The operating system a delivery team runs its information on: which channel a given message belongs in, how much the recurring calendar actually costs, how a status update survives a 20-second executive skim, and what happens when someone is blocked. Most teams never design this — it accretes, one well-intentioned meeting at a time, until 30% of the week is gone and blockers still surface three days late. When to use this skill The calendar is full and nobody can say why — you need the meeting load measured in person-hours and dollars before you can argue about it Status updates go unread — stakeholders keep asking questions the update already answered, which means it is not skimmable Blockers surface late — a problem that existed Monday first appears in Thursday's status, because there is no escalation path with an SLA A team goes distributed or adds a third timezone — the sync-heavy rhythm that worked co-located silently taxes one region Recurring "should this be a meeting?" arguments — you need a routing rule the team agreed to in advance, not a per-case negotiation New team formation — write the charter on day one, before the calendar fills with rituals nobody will later feel able to cancel Inputs the skill expects A calendar export of recurring meetings: title, duration, cadence, attendees, day and start time (UTC) The people involved with roles, timezones, and fully-loaded hourly cost Recent decision counts per recurring meeting (last month), plus whether each has an agenda and written notes A draft status update, or a recent one that failed to land The team's core-hours overlap and current escalation path, if either exists What is currently going wrong: unread updates, late blockers, or calendar load Clarify First Before generating, confirm these inputs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/team-communications