Weekly review

Skill moses607/skillforge/skills/weekly-review

SkillForge — production-ready Claude & Claude Code skills for developers, knowledge workers, and marketers. 9 free skills (MIT) + a Pro pack.

Install

npx -y skills add moses607/skillforge --skill weekly-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
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 author says it does

Copied from the file, not written here

Run a structured weekly review that captures loose ends, closes the past week, and plans the next one. Use whenever the user asks to "do my weekly review", "plan my week", "help me reset", "what should I focus on", mentions GTD, a Friday/Sunday review, or dumps a pile of tasks and half-finished threads needing order. Trigger on any weekly planning or reset request.

SKILL.md

2.5 KB, as published. Nobody here has run it

Weekly Review

A weekly review turns a scattered week into a clear next one. Run it as a guided pass, not a lecture. The goal: nothing important is silently dropped, and next week has a small set of real priorities.

The five phases

Work through them in order. Ask for input where the user's data is needed; don't invent their commitments.

1. Capture (empty the head) Prompt for open loops: unfinished tasks, unanswered messages, "I keep meaning to…" items, commitments made to others. List them all before judging any.

2. Clarify For each captured item, force one outcome:

Actionable? → next physical action (verb-first).
Not actionable but keep? → reference or someday/maybe.
Trash? → drop it explicitly (saying "drop this" is a decision, not a failure).

3. Reflect on the week that ended

What actually moved forward? (name wins — momentum compounds)
What stalled, and why? (was it capacity, clarity, or motivation? each has a different fix)
What did I say yes to that I shouldn't have?

4. Prioritize next week Pick 3 outcomes max that would make next week a success. More than 3 "top" priorities means none are. For each, name the single first action.

5. Calendarize Match the 3 outcomes to real time blocks against known commitments. Flag over-commitment honestly: if the 3 priorities need 15h and the week has 6h free, say so and cut.

Output template

## Weekly review — week of <date>

### Wins this week
- ...

### Stalled / carried over
- <item> — <why it stalled> → <next action>

### Dropped (consciously)
- ...

### Next week — 3 priorities
1. <outcome> → first action: <verb-first>
2. ...
3. ...

### Time reality check
<Do the 3 priorities fit the free hours? If not, what gets cut or moved.>

Rules

Cap top priorities at 3. Push back if the user lists more.
Every stalled item leaves the review with a concrete next action or an explicit "dropped".
Be honest about capacity — an inspiring plan that doesn't fit the week just breeds guilt.
Don't moralize about the stalled items; name the cause and move on.