Weekly Review Skill for Claude
> Synthesize a week of inputs (calendar, tasks, journal, OKR check-ins) into a structured review with wins, learnings, blockers, and next-week priorities. Use for a Friday/Sunday weekly review, GTD review, or OKR check-in.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/borghei/Claude-Skills --skill weekly-reviewWhat comes with it
12 124 bytes besides the instructionThe instruction itself
13 sections, as written by the authorWeekly Review
Synthesize a week into a structured review covering wins, learnings, blockers, and next-week priorities.
Keywords
weekly review, GTD, getting things done, OKR check-in, retrospective, weekly retro, journal, reflection, end of week, EOW
Clarify First
Before synthesizing the review, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] The week's raw inputs — actual wins, learnings, and blockers; this is the content the review synthesizes, not invented
- [ ] OKR / goal progress — current numbers vs target drives the check-in section and flags drift
- [ ] Next-week priorities — the top 1-3 commitments the review must end on
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
- Fill in
assets/weekly_review_input.jsonwith the past week's wins, learnings, blockers, OKR progress - Run:
python scripts/weekly_review_synthesizer.py weekly_review_input.json - Save the output as your week's review
Core Workflows
Workflow 1: Standard Friday Review (30 min)
- Capture 3-5 wins from the past week
- Capture 1-3 learnings (what surprised you, what you got wrong)
- Capture top 1-3 blockers / risks for next week
- Update OKR / goal progress
- List top 3 priorities for next week
- Run synthesizer
Time Estimate: 30-45 minutes weekly.
Workflow 2: Bootstrap (First Time)
- Read
references/weekly_review_methodology.md - Decide cadence (Friday afternoon vs Sunday evening — both work)
- Block 30-45 min recurring on calendar
- Use input template; tune over 4 weeks until format works for you
Time Estimate: 1 hour to set up; 30-45 min weekly thereafter.
Workflow 3: Quarterly Pattern Review
- Save weekly reviews in a single folder
- Quarterly: read all 12-13 weeks
- Look for patterns: recurring blockers, energy patterns, OKR drift
- Adjust cadence, cadence, or commitments based on patterns
Time Estimate: 1-2 hours quarterly.
Tools
weekly_review_synthesizer.py
Reads structured weekly input JSON and produces a markdown weekly review.
python scripts/weekly_review_synthesizer.py input.json
python scripts/weekly_review_synthesizer.py input.json --json
Reference Guides
references/weekly_review_methodology.md— GTD weekly review, OKR check-in patterns, common pitfalls
Templates
assets/weekly_review_input.json— Input template
Best Practices
- Block the time. 30 min recurring; defend against rescheduling.
- Same time each week. Habits stick when the trigger is consistent.
- Capture the pattern, not the noise. Weekly review is a layer above the moment-to-moment task list.
- OKR check-in over chase. Weekly OKR progress is signal; quarterly is the action moment.
- Compound across weeks. Reviews are most useful when read in batches.
- Don't over-format. A messy review you actually do beats a perfect one you skip.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take borghei/weekly-review from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.