How do I install the Status Report skill?

Run npx skillmds@latest add spillwavesolutions/status-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Status Report skill do?

Generate a status report. Use when asked for a status report, a standup summary, "what changed this week", or "what did we ship". Writes docs/status/ - .md, commits, and publishes — never paste an unrecorded status into chat. It is listed under Docs & Writing on SkillMD.

Is Status Report safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Status Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Status Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Status Report?

spillwavesolutions (@spillwavesolutions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Status Report by spillwavesolutions

Name: Status Report
Author: spillwavesolutions

Status Report

Generate a status report. Use when asked for a status report, a standup summary, "what changed this week", or "what did we ship". Writes docs/status/<date>-<kind>.md, commits, and publishes — never paste an unrecorded status into chat.

File contents

Status report

Pick the kind from the ask: daily (the standup — terse, item-level), weekly (the stakeholder rollup — epic-level), or timecard (the billing narrative — a sentence or two per day; §17 Q4 is closed: no hours).
Run bin/worklog status --kind <kind> --emit-facts and read the JSON. For a timecard, add --since YYYY-MM-DD --until YYYY-MM-DD when the ask names a window (default: the last 7 days). Every claim in the report comes from these facts — not from memory of the session.
Write the prose per §13.3's shapes:
- daily — terse bullets, fits on a screen: Shipped / In flight (with ages — a 9-day-old "in progress" is the whole story) / Blocked (and by what) / Unplanned / Needs attention (conflicts, deferred syncs).
- weekly — prose plus tables grouped by epic: what shipped, slippage (still open despite being in flight at the window start), the unplanned rollup with the percentage of closed items that were unplanned, and what's next.
- timecard — ONE SHORT PARAGRAPH PER DAY: a sentence or two saying what the day consisted of, in plain language, under a day heading like ## Monday, 14 July. No tables, no ticket IDs in the reading path, no status columns. Days without activity are omitted, not padded.
THE UNPLANNED SECTION IS THE POINT — always include it (in a timecard, as prose in the day's paragraph, never as a percentage).
Pipe the prose to bin/worklog status --kind <kind> --write (timecard: repeat the same --since/--until; the file lands at docs/status/<until>-timecard.md). Commit the report file, together with the log/roadmap if they were touched.
Run bin/worklog triggers status-report. Publish via the wiki-publish skill flow (key status/<date>-<kind>; timecard: status/<until-date>-timecard) only if wiki-publish or wiki-publish:status is listed. An empty list means write the file and stop — do not publish. Status reports are frozen — publish once, never re-publish.

Never regenerate an existing report (invariant 15.9). If a report was wrong, the correction goes in the next report, not into the old one.

---name: status-reportdescription: Generate a status report. Use when asked for a status report, a standup summary, "what changed this week", or "what did we ship". Writes docs/status/<date>-<kind>.md, commits, and publishes — never paste an unrecorded status into chat.---# Status report1. Pick the kind from the ask: `daily` (the standup — terse, item-level), `weekly` (the stakeholder rollup — epic-level), or `timecard` (the billing narrative — a sentence or two per day; §17 Q4 is closed: no hours).2. Run `bin/worklog status --kind <kind> --emit-facts` and read the JSON. For a timecard, add `--since YYYY-MM-DD --until YYYY-MM-DD` when the ask names a window (default: the last 7 days). Every claim in the report comes from these facts — not from memory of the session.3. Write the prose per §13.3's shapes: - **daily** — terse bullets, fits on a screen: Shipped / In flight (with ages — a 9-day-old "in progress" is the whole story) / Blocked (and by what) / Unplanned / Needs attention (conflicts, deferred syncs). - **weekly** — prose plus tables grouped by epic: what shipped, slippage (still open despite being in flight at the window start), the unplanned rollup with the percentage of closed items that were unplanned, and what's next. - **timecard** — ONE SHORT PARAGRAPH PER DAY: a sentence or two saying what the day consisted of, in plain language, under a day heading like `## Monday, 14 July`. No tables, no ticket IDs in the reading path, no status columns. Days without activity are omitted, not padded. THE UNPLANNED SECTION IS THE POINT — always include it (in a timecard, as prose in the day's paragraph, never as a percentage).4. Pipe the prose to `bin/worklog status --kind <kind> --write` (timecard: repeat the same `--since`/`--until`; the file lands at `docs/status/<until>-timecard.md`). Commit the report file, together with the log/roadmap if they were touched.5. Run `bin/worklog triggers status-report`. Publish via the wiki-publish skill flow (key `status/<date>-<kind>`; timecard: `status/<until-date>-timecard`) only if `wiki-publish` or `wiki-publish:status` is listed. An empty list means write the file and stop — do not publish. Status reports are frozen — publish once, never re-publish.Never regenerate an existing report (invariant 15.9). If a report was wrong,the correction goes in the next report, not into the old one.

Frequently asked questions