Status reports
Write clear project and program status reports for stakeholders. Use whenever the user asks for a weekly status, program update, executive status, RAG status, or progress report on a project or initiative.From its SKILL.md
npx -y skills add shinzoxD/knackbox --skill status-reportsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.4 KB, 250 tokens by cl100k_base, as published. Nobody here has run it
Status Reports
Status is for decisions, not diaries. Lead with health, then deltas, then asks.
Default format
# Status: <project> — <date>
**Overall:** Green | Yellow | Red — one sentence why
## Highlights (since last update)
- …
## Progress vs plan
| Workstream | Status | Notes |
## Risks / blockers
| Risk | Impact | Mitigation | Owner |
## Asks / decisions needed
1. …
## Next period plan
- …
## Metrics (if any)
…
Rules
- Color must match the narrative; no Green with hidden P0.
- Prefer outcomes over activity ("Shipped X" not "Worked on X").
- Quantify when numbers exist; never invent KPIs.
- Make asks explicit with owners and dates.
- Keep exec versions ≤ 1 page; link details.
- Separate customer-facing incidents (use incident-comms) from project status.
Edge cases
- Multi-team program: roll-up with per-stream RAG.
- No progress: say so; replan rather than pad.
- Confidential: scrub names/data as required.
What ships with it: 1 file
1.2 KB alongside SKILL.md
benchmarks/
- prompts.json1.2 KB