status-update
Skill2 starsChanged 58 days agoMITView on GitHub
Create concise status updates for teams, managers, executives, customers, or partners.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- CSPulse/customer-success-skillstheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- Robinnnnn/skillstheir own version, first seen Nov 1, 2026
- lost-rob0t/skillstheir own version, first seen Oct 30, 2026
- The-AI-Thinker/claude-code-pm-startertheir own version, first seen Oct 15, 2026
- Baba01hacker666/dummyskillstheir own version, first seen Oct 13, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- etrebels/claude-code-growth-os★ 21same name
- arezous/pm-pilot★ 20same name
- The-AI-Thinker/claude-code-pm-starter★ 13same name
- caidanw/skills★ 11same name
- Robinnnnn/skills★ 4same name
- CSPulse/customer-success-skills★ 2same name
- tines/skills★ 1same name
- Baba01hacker666/dummyskills★ 0same name
- lost-rob0t/skills★ 0same name
- nbirkner/digital-brain★ 0same name
1 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brief-meSkill
- clear-askSkill
- decision-briefSkill
- follow-up-draftSkill
- meeting-to-actionsSkill
- reduce-to-factsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
9
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 10
Create a concise update from messy conversation state without losing the ask, risk, or next milestone.
- Distinctive: line 31
Do not send the update unless explicitly asked.
- Distinctive: line 32
Keep risks separate from blockers.
- Distinctive: line 35
Keep the output short enough to send quickly.
- Distinctive: line 39
Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the …
- Distinctive: line 41
Use the smallest useful output.
- Distinctive: line 43
When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a …
- Distinctive: line 46
Keep unresolved approvals, owners, timing, and blockers explicit in the update.
- Distinctive: line 47
Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
“Common” is measured: kept by at least 6 in 10 of the 11 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-update
Purpose
Create a concise update from messy conversation state without losing the ask, risk, or next milestone.
Modes
- team
- manager
- executive
- customer / partner
Inputs
- Slack or email context
- Project or ticket context
- Meeting notes
- Customer context
- Pasted update notes
- A
reduce-to-factsledger or conversation-state record
Guardrails
- Read before write.
- Do not send the update unless explicitly asked.
- Keep risks separate from blockers.
- Tune tone and detail to the audience.
- Label assumptions and source gaps.
- Keep the output short enough to send quickly.
Portable Output Contract
- Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action.
- Use the smallest useful output.
- Label assumptions and preserve source gaps, source anchors, and confidence labels.
- When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support.
- Keep unresolved approvals, owners, timing, and blockers explicit in the update.
- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
Output
- Conversation state
- Status
- What changed
- Progress
- Risks / blockers
- Stakeholder sensitivities
- Asks
- Next milestone
- Suggested audience-specific version
Success Standard
The user should get a send-ready update in under 5 minutes.
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.