status-report
The facts
Its description
Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.
The description the agent reads to decide when to use it.
When it starts
The agent would pick this skill when someone asks for a written status update for leadership or stakeholders — a weekly, monthly, or quarterly report that pulls together KPIs, project health, risks, and decisions needed. It also fits when someone wants a pile of project tracker activity turned into a readable narrative.
Things a person might say (the model's guesses)
- “Write my weekly status report for the platform team”
- “I need a monthly update for leadership on the migration project”
- “Turn all this project tracker activity into a status report with risks and action items”
A model's summary of when it is used.
What it takes when started
[weekly | monthly | quarterly] [project or team]
What to type after its name when you start it.
Licence
Apache-2.0, from LICENSE
The terms its author shares it under, which let it be shown here.
The text
Most marks come from matching words in the file, so treat them as pointers.
/status-report
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a polished status report for leadership or stakeholders. See the risk-assessment skill for risk matrix frameworks and severity definitions.
Raw lines 1 to 12Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
Output
## Status Report: [Project/Team] — [Period]
**Author:** [Name] | **Date:** [Date]
### Executive Summary
[3-4 sentence overview — what's on track, what needs attention, key wins]
### Overall Status: 🟢 On Track / 🟡 At Risk / 🔴 Off Track
### Key Metrics
| Metric | Target | Actual | Trend | Status |
|--------|--------|--------|-------|--------|
| [KPI] | [Target] | [Actual] | [up/down/flat] | 🟢/🟡/🔴 |
### Accomplishments This Period
- [Win 1]
- [Win 2]
### In Progress
| Item | Owner | Status | ETA | Notes |
|------|-------|--------|-----|-------|
| [Item] | [Person] | [Status] | [Date] | [Context] |
### Risks and Issues
| Risk/Issue | Impact | Mitigation | Owner |
|------------|--------|------------|-------|
| [Risk] | [Impact] | [What we're doing] | [Who] |
### Decisions Needed
| Decision | Context | Deadline | Recommended Action |
|----------|---------|----------|--------------------|
| [Decision] | [Why it matters] | [When] | [What I recommend] |
### Next Period Priorities
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]If Connectors Available
If ~~project tracker is connected:
- Pull project status, completed items, and upcoming milestones automatically
- Identify at-risk items and overdue tasks
If ~~chat is connected:
- Scan recent team discussions for decisions and blockers to include
- Offer to post the finished report to a channel
If ~~calendar is connected:
- Reference key meetings and decisions from the reporting period
Tips
- Lead with the headline — Busy leaders read the first 3 lines. Make them count.
- Be honest about risks — Surfacing issues early builds trust. Surprises erode it.
- Make decisions easy — For each decision needed, provide context and a recommendation.
From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.