status-report
Skill1 starsChanged 5 months agoMITView on GitHub
Write a concise project or program status report with an overall RAG (red/amber/green) health rating, progress since last update, what's next, risks/blockers, and explicit asks. Use when the user says "write a status report", "weekly update", "status update", "where are we on X", or needs a stakeholder-ready progress summary.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- angusfretwell/skillstheir own version, first seen Oct 13, 2026
- Lwhieldon/claude-project-mgmt-playbooktheir own version, first seen Oct 13, 2026
- microsoft/amplifier-agenttheir own version, first seen Oct 13, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- Arasz/ai-badgertheir own version, first seen Oct 11, 2026
Used with
Projects with it also use 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.
claude-office-skillsSkillmeeting-notes
>
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- anthropics/knowledge-work-plugins★ 35ksame name
- shiwenwen/hope-agent★ 1.9ksame name
- oswarld/notion-skills★ 11same name
- microsoft/amplifier-agent★ 9same name
- Lwhieldon/claude-project-mgmt-playbook★ 4same name
- Arasz/ai-badger★ 3same name
- Joshua-Palamuttam/workbench-template★ 3same name
- openstatusHQ/skills★ 2same name
- sabirmgd/terminal-first-goal-loop★ 2same name
- angusfretwell/skills★ 1same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- capacity-planningSkill
- decision-logSkill
- dependency-mappingSkill
- escalationSkill
- estimation-sizingSkill
- exec-summarySkill
- launch-readinessSkill
- okr-trackingSkill
- postmortemSkill
- prd-reviewSkill
- program-health-dashboardSkill
- project-charterSkill
- raid-logSkill
- release-notesSkill
- retrospectiveSkill
- roadmap-planningSkill
- sprint-planningSkill
- stakeholder-comms-planSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
2
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
- Distinctive: line 19
If available, prior report (to show deltas) and target dates.
- Distinctive: line 32
Keep it short; link out for detail.
“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.
Files
Status Report
Produce a scannable status update a busy stakeholder can read in under a minute.
When to use
- Recurring project/program updates (weekly, biweekly) for stakeholders or leadership.
- An ad-hoc "where are we?" snapshot.
Inputs to gather
- Reporting period and audience (team vs. exec changes the altitude).
- What got done since last update; what's planned next.
- Current blockers/risks and any decisions or help needed.
- If available, prior report (to show deltas) and target dates.
Process
- Set an overall RAG status and one-line rationale:
- 🟢 Green — on track. 🟡 Amber — at risk, has a plan. 🔴 Red — off track, needs intervention.
- Lead with a TL;DR (2–3 sentences): health, biggest progress, biggest risk.
- List progress as completed outcomes (not activity). Show schedule deltas vs. plan.
- List next — the few things that matter most for the coming period.
- Surface risks/blockers with owner and mitigation.
- End with asks — specific, addressed to a named person, with a needed-by date. Omit if none.
Style
- Outcomes over activity. Numbers over adjectives. Be honest about amber/red — hiding slippage erodes trust.
- Keep it short; link out for detail.
Output format
Use templates/status-template.md.
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
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.