agentleFS
etrebelsetrebels/claude-code-growth-os/.claude/skills/status-update/SKILL.md

status-update

Skill21 starsChanged 2 months agoMITView on GitHub

Draft a short status update from recent daily-log entries. Trigger when the user asks for a status update, a weekly update, or "what should I tell my team / manager / board".

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    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:

    Read the last five to seven entries.

    line 10
  2. Distinctive:

    Write three bullets: what moved, what's blocked, what's next.

    line 11
  3. Distinctive:

    Keep it under 120 words. Lead with the outcome, not the activity.

    line 12

“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.

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

Status Update

Draft a short update a busy stakeholder would actually read, from ops/daily-log.md:

  1. Read the last five to seven entries.
  2. Write three bullets: what moved, what's blocked, what's next.
  3. Keep it under 120 words. Lead with the outcome, not the activity. No filler.

Offer to save it to ops/updates/<date>.md.

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.