agentleFS
pobstetapobsteta/aigora/.claude/skills/weekly-review/SKILL.md

weekly-review

Skill0 starsChanged 46 days agoMITView on GitHub

Structured weekly business review and planning session. Use when user says "weekly review", "let's do a review", "what happened this week", or at the start of a new week.

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

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the past 7 days of daily logs from memory/logs/:

    line 15
  2. Distinctive:

    If logs don't exist for some days, note which days are missing

    line 17
  3. Very specific:

    Update the goals.md topic file in Claude Code's native project memory folder with new priorities if they've changed (Write tool).

    line 62
  4. Distinctive:

    Create next Monday's daily log template with the priorities

    line 63
  5. Distinctive:

    Ask user if any goals need adjustment

    line 64
  6. Distinctive:

    If logs are sparse, note this and suggest better logging habits

    line 76
  7. Distinctive:

    Keep the review concise — scannable in 5 minutes

    line 77

“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

Structured review of the past week and planning for the next.

Process

Step 1: Gather Data

Read the past 7 days of daily logs from memory/logs/:

  • Today's log and the 6 preceding days
  • If logs don't exist for some days, note which days are missing

Read current goals and priorities from Claude Code's native auto-memory: open the goals.md topic file in Claude Code's native project memory folder (or whatever topic file holds them, check MEMORY.md index) with the Read tool. If goals haven't been captured yet, ask the user for them and write them to goals.md.

Optionally run scripts/weekly_metrics.py to parse log files for patterns.

Step 2: Review Format

Present the review in this structure:

## Weekly Review: [Week of Mon DD - Sun DD]

### What Happened This Week
- [Key events, meetings, decisions from logs]
- [Notable accomplishments]
- [Unexpected issues or changes]

### What Got Done
- [Completed tasks and deliverables]
- [Progress on goals from `goals.md` topic file]

### What Didn't Get Done
- [Tasks that slipped]
- [Why they slipped (if apparent from logs)]

### Patterns & Insights
- [Recurring themes across the week]
- [Time spent on different categories]
- [Energy observations — what drained, what energized]

### Next Week's Plan
- **Priority 1:** [Most important thing]
- **Priority 2:** [Second most important]
- **Priority 3:** [Third most important]
- **Carry-over:** [Tasks from this week that roll forward]

### Goals Check
- [Progress against 90-day goals from `goals.md` topic file]
- [Any goal adjustments needed?]

Step 3: Update Memory

After the review:

  1. Update the goals.md topic file in Claude Code's native project memory folder with new priorities if they've changed (Write tool). If the topic file doesn't exist yet, create it and add a pointer line to MEMORY.md.
  2. Create next Monday's daily log template with the priorities
  3. Ask user if any goals need adjustment

Script

scripts/weekly_metrics.py — Parses daily logs and extracts:

  • Number of events per day
  • Common themes/keywords
  • Tasks mentioned as completed

Rules

  • Be honest about what didn't get done — don't spin it
  • If logs are sparse, note this and suggest better logging habits
  • Keep the review concise — scannable in 5 minutes
  • The planning section is the most important output — make it actionable

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.