status-report
Skill1 starsChanged 2 months agoMITView on GitHub
Compose a stakeholder status update from recent work — git history plus the current conversation; PL or EN to match the audience.
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
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 repository28 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- architect-reviewSkill
- article-writingSkill
- changelog-watchSkill
- coordinator-workersSkill
- cost-forecastSkill
- design-docSkill
- documentSkill
- ea-briefingSkill
- estimateSkill
- eval-toolSkill
- gh-ticketsSkill
- headless-loopSkill
- interview-guideSkill
- job-supervisorSkill
- market-researchSkill
- meeting-notesSkill
- migration-planSkill
- obsidian-noteSkill
- plan-to-issuesSkill
- postmortemSkill
- readSkill
- release-notesSkill
- skill-stocktakeSkill
- slide-deckSkill
- threat-modelSkill
- tradeoff-tableSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read ./CONTEXT.md if present.
- Distinctive: line 14
Write four sections: Done, In progress, Blocked / risks, Next.
“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
Read ./CONTEXT.md if present. Build a status update for the period and audience in
$ARGUMENTS (default period: since last Monday; default audience: technical peers).
- Gather what actually happened:
git log --since=...in this repo, the current conversation, and any notes passed in$ARGUMENTS. Outcomes, not commit messages — translate "what changed" into "what the reader can now see, use, or stop waiting for". - Write four sections: Done, In progress, Blocked / risks, Next. If a section is empty, say "nothing" — never pad.
- Match the audience: language (PL or EN), and altitude — no commit hashes or file paths for executives; keep them for engineering audiences.
Markdown only. State the covered period at the top. Don't invent progress: if something can't be
verified from the sources above, leave it out or mark it TODO: confirm. For a changelog or
release notes rather than a stakeholder update, use the release-notes skill.
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.