Individual skill
weekly-review
Runs a timeboxed weekly review - empty every inbox to a decision, audit every open commitment, and pick the 3-5 outcomes that define next week. Use when someone asks "walk me through a weekly review", "help me plan my week", "my task system feels stale and I don't trust it", or "I keep dropping commitments". Do NOT use for setting up the underlying capture-and-organize system itself - use gtd-system instead - or for tracking long-horizon personal goals with an accountability loop - use goals-accountability instead.
skills/weekly-review/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- security Derived category
- productivity Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,624 bytes
Read excerpt
# Weekly Review
The weekly review is the maintenance ritual that keeps a productivity system trustworthy. Skip it two weeks in a row and the lists go stale, the brain stops trusting them, and everything moves back into working memory - which is the exact failure the system existed to prevent. Run it as a repeatable checklist at a fixed time, not as a guilt session, and it takes 60-90 minutes to buy a week of clear-headed execution.
## Operating procedure
The three phases run in this order because each depends on the last: you cannot audit projects honestly (get current) while unprocessed inputs hide commitments (get clear), and you cannot pick next week's outcomes (get ahead) from a project list you have not audited.
### Step 1: gather inputs (5 minutes)
Collect before starting; if the user cannot produce one, note it as a gap in their system and continue.
- The list of inboxes. Default set: email, chat, notes app, task-manager inbox, physical desk/papers. If they name fewer than three, ask where meeting commitments land - there is almost always a hidden inbox.
- The project list, waiting-for list, and someday/maybe list.