status-comms
Skill4 starsChanged 35 days agoMITView on GitHub
Draft the same project status story in multiple formats - a status email, slide bullets, or a dashboard narrative - tuned to the audience. Use when asked for a status email, executive update, or slide-ready status. Usage - /status-comms audience and format, plus the data source
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-requestSkill
- code-review-lightSkill
- deliverable-qaSkill
- exec-summarySkill
- meeting-prepSkill
- sow-reviewSkill
- stakeholder-prepSkill
- status-reportSkill
- transcript-actionsSkill
- weekly-briefSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
If a status-data.csv or project notes are referenced, read them.
- Very specific: line 56
If the user wants an actual .pptx or .docx file rather than bullets, Claude's built-in document skills can build one from this content when …
- Distinctive: line 62
Every format ends with: *Drafted with Claude Code on YYYY-MM-DD.
- Distinctive: line 66
When status is 🔴 Red or the situation is sensitive:
- Distinctive: line 71
Avoid hedging language such as "we believe," "hopefully," or "it seems." Replace with direct statements or explicit uncertainty: "we do not …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Status Communications
Draft multi-format status communications from project data or a conversational summary of the week. One status story, formatted for each audience that needs it.
Step 1: Understand What's Needed
Determine from $ARGUMENTS and the conversation:
- Audience: Who is receiving this? (Client executive, internal team, steering committee, project sponsor)
- Format: Email, slide bullets, dashboard narrative, formal report, or all of the above
- Source data: CSV status file, free-text summary, or conversation context
- Tone: How sensitive is the current situation? Is there bad news to communicate?
If a status-data.csv or project notes are referenced, read them. If the /status-report skill
already produced a report this session, build from it rather than re-deriving the status.
Step 2: Assess and Summarize Status
Before drafting, synthesize:
- Overall RAG status (🔴 Red / 🟡 Amber / 🟢 Green) with specific rationale. Present it as a proposal for the delivery lead to confirm.
- Key wins this period
- Active risks or issues and their trajectory (getting better, stable, getting worse)
- Notable upcoming milestones in the next 2 weeks
Step 3: Draft in the Requested Format(s)
Email Format
Professional status email suitable for forwarding to client stakeholders.
Subject line: [Project Name]: Week [#] Status Update | [RAG Status]
Structure:
- Opening sentence: overall status and one-line summary
- Accomplishments: 3 to 5 bullets
- Upcoming: 3 to 5 bullets with dates
- Risks/Issues: brief table or 2 to 3 bullets
- Actions needed from client: explicit asks, if any
- Closing
PowerPoint / Slide Format
Short bullets optimized for a status slide:
- Overall: [RAG]: [one-line rationale]
- Accomplishments: 3 to 5 bullets (10 words or fewer each)
- Next 2 weeks: 3 to 5 bullets with dates
- Key risks: 2 to 3 bullets with owner
- Actions: table with Action | Owner | Due Date
If the user wants an actual .pptx or .docx file rather than bullets, Claude's built-in
document skills can build one from this content when they are available in the session.
Dashboard / Narrative Format
2 to 3 paragraph narrative suitable for a project management dashboard or executive briefing note.
Every format ends with: Drafted with Claude Code on YYYY-MM-DD; reviewed by [NAME]
Handling Bad News
When status is 🔴 Red or the situation is sensitive:
- Lead with facts, not apologies
- State the issue clearly in the first sentence
- Immediately follow with: what caused it, what is being done, and by when the situation will be resolved or re-assessed
- Avoid hedging language such as "we believe," "hopefully," or "it seems." Replace with direct statements or explicit uncertainty: "we do not yet know X; we will have an answer by [date]"
Bad news delivered by a person is a competence signal. Delivered only by a document, it reads as a complaint. Draft the message; recommend the delivery lead deliver it in person or by call first, with the written version as the record.
Tone Calibration
| Audience | Tone | Lead With |
| C-suite / Board | Concise, decisive | Bottom line, then evidence |
| Project sponsor | Direct, collaborative | Status + what you need |
| Internal team | Frank, action-focused | Issues + next steps |
| Client PM | Professional, detailed | Accomplishments + risks |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

