agentleFS
cogotemartinezcogotemartinez/ai-second-brain-template/.claude/skills/weekly-review/SKILL.md

weekly-review

Skill9 starsChanged 9 months agoMITView on GitHub

Guided weekly reflection across all your domains

99 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quarterly-review, daily-plan and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Phoenixrr2113Skill

    quarterly-review

    Quarterly review — strategic look at the last 3 months. Career trajectory, project health, life balance, big decisions ahead. Runs 1st of Jan/Apr/Jul/Oct.

    Also in 3 projects that use this

  • steptianSkill

    daily-plan

    每日待办计划与日程管理。触发词:'今天要做'、'今日计划'、'今日待办'、'今天安排'、'安排一下'、'加个任务'、'记个任务'、'今日复盘'、'今日回顾'、'今天总结'、'本周计划'、'周总结'、'开始工作'、'上班了'、'完成了'、'加个日程'、'记个日程'、'改一下时间'、'日程调整'、'面试'、'开会'、'约了'。支持四象限优先级、时段分配、固定日程管理、智能时间估算、每日/每周复盘。当用户提到有明确时间的安排(如'下午两点面试'、'10点开会'),自动识别为日程并写入日程表。

    Also in 3 projects that use this

  • seedprodSkill

    daily-brief

    Send a morning briefing via Telegram with weather, news, and a motivational quote. Designed to run via launchd for automated daily delivery.

    Also in 5 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 8 projects that use this

  • Phoenixrr2113Skill

    morning-brief

    Full morning brief — calendar, email, meeting prep, execute actionable items, create follow-up tasks. Runs at 8:03 AM or when Randy asks for a morning update.

    Also in 4 projects that use this

  • JerovinoSkill

    process-inbox

    Processes tasks.md inbox items by triaging each one to its proper location in the vault

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this every Sunday or Monday to stay on top of all life areas.

    line 16
  2. Distinctive:

    Neglected domains: No activity in 2+ weeks

    line 41
  3. Distinctive:

    Update memory.md in domains where priorities changed

    line 102
  4. Distinctive:

    If any domain has alerts, suggest concrete actions for this week

    line 104

“Common” is measured: kept by at least 6 in 10 of the 85 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/weekly-review

Weekly reflection that reads all domains and produces a digest with cross-domain insights.

Usage

/weekly-review          # Full weekly review

Run this every Sunday or Monday to stay on top of all life areas.


Process

Step 1: Read All Domains

For each domain, read:

  • CLAUDE.md (current priorities, alerts)
  • memory.md (recent entries since last review)

Step 2: Extract Per-Domain Status

For each domain, identify:

  • Progress: New memory entries since last week
  • Priorities: Current priorities and their status
  • Alerts: Any red or yellow alerts triggered
  • Pending: Decisions or actions waiting

Step 3: Cross-Domain Insights

Look for:

  • Conflicts: Career goal vs health alert, spending vs savings goal
  • Synergies: Learning goal supports career priority, project could generate income
  • Neglected domains: No activity in 2+ weeks
  • Overloaded domains: Too many active items in one area

Step 4: Generate Weekly Digest

Present the review in a scannable format (see output below).

Step 5: Plan Next Week

Ask the user:

"What are your top 3 priorities for next week?"

Log their answer in the relevant domain memory.md files.


Output Format

# Weekly Review - [Date]

## Domain Status
| Domain | Activity | Top Priority | Alert |
|--------|----------|-------------|-------|
| Finances | [Active/Quiet/Stale] | [Current #1] | [None/Yellow/Red] |
| Career | ... | ... | ... |
| Health | ... | ... | ... |
| Projects | ... | ... | ... |
| Learning | ... | ... | ... |
| Relationships | ... | ... | ... |

## Wins This Week
- [Concrete win from memory entries]
- [Another win]

## Attention Needed
- [Domain with alert or no activity]
- [Pending decision that needs resolution]

## Cross-Domain Insights
- [Connection between domains]
- [Potential conflict or synergy]

## Next Week Focus
1. [Priority 1 - which domain]
2. [Priority 2 - which domain]
3. [Priority 3 - which domain]

Guidelines

  • Be honest about neglected domains — it's useful information, not a judgment
  • Keep the focus on 3 priorities max for next week — more than 3 means nothing is really prioritized
  • Flag cross-domain conflicts — these are the most valuable insights
  • Celebrate wins — even small progress matters
  • Update memory.md in each relevant domain after the review

After the Review

  1. Update memory.md in domains where priorities changed
  2. Log the review date so next week's review knows the baseline
  3. If any domain has alerts, suggest concrete actions for this week

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.