weekly-review
Performs weekly cleanup of memory and synthesizes project progress into a journal entry.
Install
mkdir -p .claude/skills/weekly-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15142" && unzip -o skill.zip -d .claude/skills/weekly-review && rm skill.zipInstalls to .claude/skills/weekly-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Weekly maintenance and synthesis. Use once a week on a day the user chooses (Thursdays and Fridays both work well), or when they ask for a "weekly review", "pattern review", or "catch-up on the week". This is the pruning cadence that keeps MEMORY accurate.Key capabilities
- →Prune stale entries from MEMORY.md
- →Identify shifting priorities in projects
- →Synthesize weekly project progress
- →Surface recurring themes and energy shifts
- →Detect intention drift and dangling mentions
- →Observe behavioral shifts in work patterns
How it works
The skill scans MEMORY.md and journal entries to identify stale information, shifting priorities, and recurring patterns, then synthesizes this into a weekly report and proposes updates.
Inputs & outputs
When to use weekly-review
- →Perform weekly project review
- →Prune memory state
- →Synthesize development progress
About this skill
A weekly review does three things: prunes stale state, synthesises the week, and surfaces patterns the day-to-day doesn't catch.
1. Prune MEMORY.md
Scan MEMORY.md for:
- Relative time with no date qualifier. "Recently", "this week", "upcoming" without an "as of YYYY-MM" anchor. Flag or update.
- Priorities that have shifted. Compare the priorities listed against what's actually been worked on in the week's journal entries. If there's drift, raise it.
- Patterns that have softened. A pattern listed six months ago may no longer be accurate. Ask before removing.
- Project-level context that's now stale. Projects that shipped, projects that got parked, projects that have moved on.
Propose updates. Apply them after the user agrees. Small changes go straight in; larger rewrites get a draft shown first.
2. Synthesise the week
Create journal/YYYY-MM-DD-weekly-synthesis.md. Frontmatter:
---
type: synthesis
tags: [weekly]
session: <session-id-if-available>
---
Cover:
- What shipped or moved forward. Concrete outcomes, not activity.
- What shifted. Priority changes, new context, decisions that altered direction.
- What got parked and why. The rationale matters more than the fact.
- Key decisions with rationale. Redundancy with individual journal entries is fine; losing the "why" isn't.
- What mattered personally. Optional — only if there's something worth preserving.
This is a synthesis, not a rehash. Connect dots across the week.
3. Surface patterns
Look across the week's journal entries for:
- Recurring themes — frustrations or topics that keep surfacing.
- Energy shifts — consistent drains or boosts the user might not have noticed.
- Intention drift — gaps between what they said they'd focus on and what actually happened.
- Dangling mentions — ideas or commitments that appeared once and went quiet.
- Behavioural shifts — changes in how they're working.
Two or three observations max. Frame as observations, not judgements. Skip this step if nothing turns up — don't pad.
When not to use it
- →The user does not request a weekly review or similar catch-up
- →The user requests a daily or ad-hoc review
Limitations
- →The skill is intended for weekly use
- →It focuses on pruning and synthesis, not daily task management
How it compares
This skill provides a structured, recurring process for maintaining project context and identifying overarching patterns, which is more systematic than ad-hoc reviews or individual journal entries.
Compared to similar skills
weekly-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| weekly-review (this skill) | 0 | 3mo | No flags | Beginner |
| notion-meeting-intelligence | 6 | 6mo | No flags | Intermediate |
| resume-handoff | 3 | 6mo | No flags | Intermediate |
| meeting-briefing | 2 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by joshfarrant
View all by joshfarrant →You might also like
notion-meeting-intelligence
openai
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
resume-handoff
parcadei
Resume work from handoff document with context analysis and validation
meeting-briefing
anthropics
Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.
personal-assistant
ailabs-393
This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or any query requiring personalized responses based on user preferences and context. On first use, collects comprehensive user information including schedule, working habits, preferences, goals, and routines. Maintains an intelligent database that automatically organizes and prioritizes information, keeping relevant data and discarding outdated context.
digital-brain
muratcankoylan
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.
meeting-sync
amanaiproduct
Sync new Granola meetings to local Knowledge folder. Use during morning planning, when user asks "what should I do today", or asks to review/sync meetings.