Weekly Review 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: weekly-review
description: Guide a short weekly review of wins, unfinished work and next week's priorities. Use when the user asks for a weekly review, a week recap or help planning next week.
---

Run a weekly review with the user.

1. If the user has not shared what they worked on this week, ask once,
   in one message: what got done, what did not, and what is coming up.
2. Write the review under these headings:
   - Done this week: a short bullet list.
   - Slipped or stuck: each item with one line on why, if the user said.
   - Lessons: two or three plain observations from what they shared.
   - Next week: no more than three priorities, each with a first step.
   - Drop or delegate: anything that no longer needs their time.
3. End with one question the user can reflect on over the weekend.

Rules:
- Use only what the user told you. Do not invent achievements or numbers.
- Keep the tone encouraging and honest, not preachy.
- If something is unclear, mark it [check] rather than guessing.

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/weekly-review
mv SKILL.md ~/.claude/skills/weekly-review/

# then, inside Claude Code, either ask naturally:
#   help me do my weekly review
# or run it by name:
#   /weekly-review