status-update
Skill13 starsChanged 3 months agoMITView on GitHub
Draft the user's status update from the active project's tasks.md and recent notes in operations/. Use when the user needs to report progress to their team, their manager, or stakeholders.
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
- Baba01hacker666/dummyskillstheir own version, first seen Oct 13, 2026
- tmusser/context-to-action-skillstheir own version, first seen Sep 16, 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
- caidanw/skills★ 11same name
- Robinnnnn/skills★ 4same name
- CSPulse/customer-success-skills★ 2same name
- tmusser/context-to-action-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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- file-feedbackSkill
- interview-synthesisSkill
- prd-reviewSkill
- setup-workspaceSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Find the state: Read the active project's tasks.md (Status notes first, then Now / Next / Blocked) and any operations/ notes dated since …
- Distinctive: line 23
Every claim of progress points at something real: a merged change, a decision made, a number moved, a meeting outcome.
- Very specific: line 25
After the user approves the draft, update tasks.md's Status notes so the next update starts from today's truth.
“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
Draft the update the user owes someone, from files, not from their memory.
Steps
- Find the state. Read the active project's
tasks.md(Status notes first, then Now / Next / Blocked) and anyoperations/notes dated since the last update. If several projects are active, ask which ones the update covers. - Ask two things only: who the update is for, and where it will be posted (email, Slack, a doc). Skip the questions if the conversation already says.
- Draft it in the user's voice per
context/preferences.md. Default shape, unless preferences say otherwise:- One line on the headline: the single most important thing that moved or didn't.
- What shipped or progressed, with the concrete result.
- What's blocked, with the specific ask that would unblock it. An update without an ask is a diary entry.
- What's next.
- Match the channel. Slack gets short lines and no headings; email gets a subject line; a doc gets the full shape.
Rules
- Every claim of progress points at something real: a merged change, a decision made, a number moved, a meeting outcome. No "good progress on X".
- Blockers name the blocker, not just the feeling. "Waiting on legal's read of the data clause since the 12th" beats "legal is slow".
- After the user approves the draft, update
tasks.md's Status notes so the next update starts from today's truth.
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.