PluginBench
Skill
Official
Pass
Audit score 90

status-report

anthropics/knowledge-work-plugins

Generate polished status reports with KPIs, risks, and action items for leadership.

What is status-report?

Creates structured status reports for weekly, monthly, or quarterly updates to stakeholders. Use this when you need to summarize project health with color-coded status, surface risks and decisions, and turn project tracker activity into a readable narrative.

  • Generates executive summary with key wins and attention areas
  • Produces color-coded overall status (green/yellow/red) with supporting metrics
  • Creates KPI table with targets, actuals, trends, and status indicators
  • Organizes accomplishments, in-progress items, risks, and decisions into structured tables
  • Identifies at-risk items and overdue tasks when project tracker is connected
  • Surfaces team decisions and blockers from recent discussions when chat is connected

How to install status-report

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill status-report
Claude Code
Cursor
Windsurf
Cline

How to use status-report

  1. 1.Run `/status-report [weekly | monthly | quarterly] [project or team]`
  2. 2.Provide project data, accomplishments, and in-progress items when prompted
  3. 3.Review the generated report structure and fill in specific metrics and risks
  4. 4.Adjust status indicators (green/yellow/red) based on actual project health
  5. 5.Add context and recommendations for any decisions requiring stakeholder input

Use cases

Good for
  • Writing a weekly status update for leadership on project health
  • Creating a monthly team report summarizing KPIs and risks
  • Turning project tracker activity into a stakeholder-ready narrative
  • Surfacing decisions that need executive approval with context and recommendations
  • Consolidating accomplishments and priorities across a reporting period
Who it's for
  • Project managers
  • Team leads
  • Engineering managers
  • Product managers
  • Anyone reporting project status to leadership

status-report FAQ

What if I don't have a project tracker connected?

You can still use the skill by manually providing project status, KPIs, and accomplishments. The report template works standalone; connectors just automate data gathering.

How detailed should the risks section be?

Include impact level and mitigation strategy for each risk. See the risk-assessment skill for severity definitions and risk matrix frameworks.

Can I customize the report format?

The skill generates a standard template optimized for leadership readability. You can edit the output after generation to match your organization's format.

What metrics should I include?

Include 3-5 key metrics most relevant to your project: delivery progress, quality metrics, resource utilization, or business KPIs. Focus on metrics that show project health.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.


name: status-report 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. argument-hint: "[weekly | monthly | quarterly] [project or team]"

/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.

Usage

/status-report $ARGUMENTS

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

  1. Lead with the headline — Busy leaders read the first 3 lines. Make them count.
  2. Be honest about risks — Surfacing issues early builds trust. Surprises erode it.
  3. Make decisions easy — For each decision needed, provide context and a recommendation.