Status Report
Turn messy sprint or tracker activity into a leadership-ready weekly or monthly status report with KPIs, RAG health, and owned action items.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill status-reportWhat is this skill?
- Markdown template with executive summary, overall green/yellow/red status, and dated author line
- KPI table with target, actual, trend, and per-metric status indicators
- Accomplishments, in-progress items with owner and ETA, and risks/issues with mitigation owners
- Argument hint for weekly, monthly, or quarterly periods and project or team scope
- Cross-links to the risk-assessment skill for severity and matrix framing
Adoption & trust: 1.5k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Grill Memattpocock/skills
Grill With Docsmattpocock/skills
Brainstormingobra/superpowers
Lark Tasklarksuite/cli
Lark Workflow Standup Reportlarksuite/cli
Cavemanjuliusbrussee/blueprint
Journey fit
Primary fit
Status reporting is core project-management work while you are building and coordinating stakeholders, so the canonical shelf is Build → PM even though the same format applies later in ship and operate cadences. The skill outputs PM artifacts (executive summary, metrics tables, in-progress grid, risks)—not code—matching the pm subphase for planning and stakeholder communication.
Common Questions / FAQ
Is Status Report safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Status Report
# /status-report > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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 ```markdown ## 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.