Design a delivery team's communication system — channel routing, meeting-load reduction, status structure, escalation SLAs, timezone norms.
SkillScore92Maintained
Automatic
◆Project Management pack
Last verified 8/20/2026
What it changes
Passed 23 of 25 test cases with the skill, and 14 of 25 without it.
Without skill56%
With skill92%
Checks it passed that the model alone missed
Classifies status update lengths over 600 words as entering the danger zone
Includes the command flag --format text when running status_update_scorer.py
Mandates assigning an expiration date of 3-6 months and a named owner upon creation
and 9 more in the full report
9 fixed14 passed either way2 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+188%
Agent turns
0%
Response time
+7%
Model gemini-3.6-flashMeasured 8/20/2026v123 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Just draft it. I need to run the Python status scoring script on a JSON draft located at `assets/draft_status.json` and get plain text output. What is the CLI command?
What was checked, without and with the skill
Checked
Without skill
With skill
Includes the command flag --format text when running status_update_scorer.py
Missed
Passed
Specifies project-management/team-communications/scripts/status_update_scorer.py as the script location
Missed
Passed
case-08 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md200 lines11 filesincludes scripts
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. If any is unknown or vague, ASK — do not assume:
Which failure you are fixing — load, unread updates, or late blockers — the three have opposite remedies; cutting meetings without installing written status makes late blockers worse