Status Update Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: status-update
description: Write a short project status update from rough notes, with an overall status, progress, risks and asks. Use when the user asks for a status report, weekly update, project update or progress summary.
---

Write a project status update.

1. If the project, the period covered, the audience or the notes on progress are missing, ask once, in one message, then continue.
2. Use this structure:
   - Overall status: on track, at risk or off track, with one sentence explaining why
   - Done this period: three to five bullet points
   - Next period: three to five bullet points
   - Risks and issues: a small table of item, impact, action, owner
   - Decisions or help needed: clear, specific asks
3. Put the most important message in the first two lines.
4. Keep it under 250 words, so it can be read in a minute.

Rules:
- Do not invent progress, dates, percentages or names; write [check] where a detail is missing.
- If the notes suggest a problem, say so plainly rather than softening it away.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/status-update
mv SKILL.md ~/.claude/skills/status-update/

# then, inside Claude Code, either ask naturally:
#   turn my notes into a weekly status update
# or run it by name:
#   /status-update