agentleFS
Sign inStart free
nisarthnisarth/claude-skills-store/skills/operations/status-report/SKILL.md

status-report

Skill1 starsChanged 7 months agoMITView on GitHub

Generate status reports with KPIs, green/yellow/red health indicators, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health, or surfacing risks needing stakeholder attention. Trigger with "status report", "weekly update", "project status", "executive summary", or "monthly report".

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use postmortem and meeting-notes.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hongyu-yuSkill

    postmortem

    Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every risk needs a mitigation.

    line 99

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Status Report Generator

Generate structured status reports with KPI tracking, health indicators, risk summaries, and action items tailored to audience.

Workflow

Step 1: Define Scope and Audience

Scope (project, team, department), period (weekly, monthly, quarterly), audience (adjust detail level), and reference the prior report for continuity.

Step 2: Gather Data

Project tracking (tasks, milestones, sprints), KPIs against targets, team updates (accomplishments, blockers), risk/issue logs, decisions needed, and external dependencies.

Step 3: Apply Health Indicators

  • GREEN: On track, meets/exceeds targets, no significant risks.
  • YELLOW: At risk, trending below target, management attention needed.
  • RED: Off track, below target, immediate intervention required.

Apply to: overall, schedule, budget, quality, scope, and team health.

Step 4: Structure the Report

Lead with health indicator and one-line summary. Highlight changes since last report. Present accomplishments, risks/issues, action items, and decisions needed.

Output Format

## Status Report: [Scope]
**Period**: [Date to Date] | **Overall**: [GREEN / YELLOW / RED]

### Executive Summary
[2-3 sentence overview]

### Health Dashboard
| Dimension | Status | Trend | Notes |
|-----------|--------|-------|-------|
| Schedule | GREEN | --> | On track for milestone |
| Budget | YELLOW | v | Trending 8% over |

### Key Metrics
| KPI | Target | Actual | Status | Trend |
|-----|--------|--------|--------|-------|

### Accomplishments
- [Completed item]

### Risks and Issues
| # | Description | Impact | Status | Mitigation |
|---|-------------|--------|--------|------------|

### Action Items
| # | Action | Owner | Due | Status |
|---|--------|-------|-----|--------|

### Decisions Needed
- [Decision] -- Needed by: [Date]

Examples

User: "Write a weekly status report for the platform migration project" Action: Gather sprint data, milestone progress, blockers, and capacity. Score health, highlight completed milestones, flag delays as YELLOW, list decisions for the steering committee.

User: "Monthly executive summary for the ops team" Action: Compile KPIs (uptime, incident count, MTTR, ticket volume), compare against targets and prior month, summarize major incidents, present headcount and budget status.

Best Practices

  • Lead with the health indicator -- executives need GREEN/YELLOW/RED first.
  • Be honest with indicators. A YELLOW that should be RED erodes trust faster than a RED with a plan.
  • Show trends, not just snapshots. GREEN trending toward YELLOW deserves mention.
  • Every risk needs a mitigation. Every action item needs an owner and deadline.
  • Be consistent in format across periods so readers can quickly find what they care about.
  • Send on a predictable schedule.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free