How do I install the Status Report skill?

Run npx skillmds@latest add nota-america/status-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Status Report safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Status Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Status Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Status Report?

nota-america (@nota-america) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Status Report by nota-america — Agent Skill

Name: Status Report
Author: nota-america

Status Report

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.

nota-america Updated Sep 17, 2026

File contents

/status-report

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md ({{ref:connectors}}).

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

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.

---name: status-reportdescription: 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.---# /status-report> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (`{{ref:connectors}}`).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 Priorities1. [Priority 1]2. [Priority 2]3. [Priority 3]```## If Connectors AvailableIf **~~project tracker** is connected:- Pull project status, completed items, and upcoming milestones automatically- Identify at-risk items and overdue tasksIf **~~chat** is connected:- Scan recent team discussions for decisions and blockers to include- Offer to post the finished report to a channelIf **~~calendar** is connected:- Reference key meetings and decisions from the reporting period## Tips1. **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.

Frequently asked questions