weekly-review
Skill24 starsChanged 5 months agoMITView on GitHub
Summarize the past week's daily notes, extracting key findings, links, action items, and potential atomic notes, and write the summary into the matching weekly note.
92 other projects use a version of this.
Adopted by
Most recently taken up by
- nicolas-diez/personal-ostheir own version, first seen Nov 8, 2026
- chrisblattman/claudeblattmantheir own version, first seen Nov 8, 2026
- totorototo/ledgertheir own version, first seen Nov 8, 2026
- TalkToHumans/pull-labtheir own version, first seen Nov 8, 2026
- Castan-AI/founder-commandstheir own version, first seen Nov 8, 2026
- jwm-axoni/claude-workbenchtheir own version, first seen Nov 8, 2026
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.
Phoenixrr2113Skillquarterly-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
steptianSkilldaily-plan
每日待办计划与日程管理。触发词:'今天要做'、'今日计划'、'今日待办'、'今天安排'、'安排一下'、'加个任务'、'记个任务'、'今日复盘'、'今日回顾'、'今天总结'、'本周计划'、'周总结'、'开始工作'、'上班了'、'完成了'、'加个日程'、'记个日程'、'改一下时间'、'日程调整'、'面试'、'开会'、'约了'。支持四象限优先级、时段分配、固定日程管理、智能时间估算、每日/每周复盘。当用户提到有明确时间的安排(如'下午两点面试'、'10点开会'),自动识别为日程并写入日程表。
Also in 3 projects that use this
seedprodSkilldaily-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-skillsSkillmeeting-notes
>
Also in 8 projects that use this
Phoenixrr2113Skillmorning-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
zephyrwang6Skilldaily-review
每日工作回顾与洞察分析,对用户前一天的对话历史和使用数据进行总结与建议
Also in 3 projects that use this
Other versions92 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 92
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- chrisblattman/claudeblattman★ 479same name
- andreaskelm/pm-brain★ 235same name
- duncan-buildroom/freeskills★ 65same name
- andrehuang/researcher-pack★ 50same name
- seandavi/lifeos-template★ 46same name
- chacosoldier/compabob★ 34same name
- cookyman74/llmwiki-harness★ 34same name
- jexchan/dailyup-second-brain-starter★ 33same name
82 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- backup-vaultSkill
- doneSkill
- extract-insightsSkill
- find-place-coordinatesSkill
- index-atomic-notesSkill
- organize-inboxSkill
- summarize-urlsSkill
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 80 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
- Distinctive: line 16
Default to the last completed week (Monday–Sunday).
- Distinctive: line 26
Read each note that exists, in chronological order.
- Distinctive: line 40
Look for recurring themes or ideas that appeared multiple times across the week.
- Distinctive: line 79
Create any of the suggested atomic notes
“Common” is measured: kept by at least 6 in 10 of the 80 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.
Files
Weekly Review
Purpose
Process a calendar week's daily notes to generate a summary that captures key insights, tracks action items, and identifies ideas worth developing into atomic notes. The summary is written into the ## Review section of that week's weekly note.
Instructions
1. Determine the target week
- Default to the last completed week (Monday–Sunday). If the user names a specific week or date, use that instead.
- Compute the weekly note name in
gggg-[W]wwformat. Use the shell to stay accurate:- Last completed week:
date -v-7d -v-mon +%G-W%V(e.g.2026-W24) - Current week:
date +%G-W%V
- Last completed week:
- The weekly note lives at
Weekly/<gggg-[W]ww>.md(e.g.Weekly/2026-W24.md). - Compute the Monday–Sunday date range for that week (e.g.
date -v-7d -v-mon +%Y-%m-%dfor the Monday, then add days).
2. Locate and read the week's daily notes
- Find daily notes in
Daily/YYYY/MM-Month/YYYY-MM-DD.mdformat for each of the 7 days. - Read each note that exists, in chronological order. Skip days with no note.
3. Extract and summarize
For each daily note, identify:
| Category | What to look for |
| Key findings | Insights, learnings, realizations, decisions made |
| Relevant links | URLs, references, resources worth revisiting |
| Action items | Tasks mentioned, TODOs, follow-ups needed |
4. Identify emergent topics
Look for recurring themes or ideas that appeared multiple times across the week. These are candidates for atomic notes.
Signs of an emergent topic:
- Mentioned in more than one of the daily notes
- An insight that surprised or shifted thinking
- A connection between previously unrelated ideas
- Something worth remembering long-term
5. Write the review into the weekly note
The weekly note's ## Review section already contains three empty subsections (created from the template):
### Key Findings
-
### Potential Atomic Notes
-
### Action Items
- [ ] Fill them in:
- Key Findings — summarized insights from the week, one bullet each. Reference the relevant
[[wikilinks]]inline rather than listing links separately — the source daily notes are already linked from the## Dayslist, so a standalone link dump would just duplicate them. - Potential Atomic Notes —
- **[Proposed title as insight]**: [why it deserves its own note]. - Action Items —
- [ ]task per outstanding follow-up.
Then write it to Weekly/<gggg-[W]ww>.md:
- If the weekly note exists: populate the three subsections under
## Reviewin place — replace the empty placeholder bullets with your content, and leave the rest of the note (Days, anything the user added) untouched. If the user has already written content under a subsection, append rather than overwrite. - If the weekly note does not exist: create it from
Meta/Templates/Weekly Note Template.md. The template uses Templater syntax (<% %>), which only runs inside Obsidian — so render the equivalent content yourself: thenote/weeklytag, a# Week ww, ggggheading, the date range, a## Dayslist linking each day ([[YYYY-MM-DD|dddd, MMM D]]), and the## Reviewsection with the three subsections filled in.
6. Confirm and offer next steps
Report which weekly note was written to. Then ask the user if they'd like to:
- Create any of the suggested atomic notes
- Move action items into their Focus section or elsewhere
- Explore any topic in more depth
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
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.

