agentskills.codes
WE

weekly-review

by joshfarrantSource

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.

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.zip

Installs 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.
256 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)

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.

Search skills

Search the agent skills registry