weekly-review
Skill0 starsChanged 4 months agoMITView on GitHub
Run a structured weekly review that captures loose ends, closes the past week, and plans the next one. Use whenever the user asks to "do my weekly review", "plan my week", "help me reset", "what should I focus on", mentions GTD, a Friday/Sunday review, or dumps a pile of tasks and half-finished threads needing order. Trigger on any weekly planning or reset request.
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 repository8 other files it gives its agents.
- commit-craftSkill
- inbox-triageSkill
- incident-postmortemSkill
- landing-copySkill
- meeting-to-actionsSkill
- newsletter-forgeSkill
- pr-review-guardianSkill
- social-repurposeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 80 edited versions we read keep these.
3
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 20
Not actionable but keep? → reference or someday/maybe.
- Distinctive: line 60
Every stalled item leaves the review with a concrete next action or an explicit "dropped".
- Distinctive: line 62
Don't moralize about the stalled items.
“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
A weekly review turns a scattered week into a clear next one. Run it as a guided pass, not a lecture. The goal: nothing important is silently dropped, and next week has a small set of real priorities.
The five phases
Work through them in order. Ask for input where the user's data is needed; don't invent their commitments.
1. Capture (empty the head) Prompt for open loops: unfinished tasks, unanswered messages, "I keep meaning to…" items, commitments made to others. List them all before judging any.
2. Clarify For each captured item, force one outcome:
- Actionable? → next physical action (verb-first).
- Not actionable but keep? → reference or someday/maybe.
- Trash? → drop it explicitly (saying "drop this" is a decision, not a failure).
3. Reflect on the week that ended
- What actually moved forward? (name wins — momentum compounds)
- What stalled, and why? (was it capacity, clarity, or motivation? each has a different fix)
- What did I say yes to that I shouldn't have?
4. Prioritize next week Pick 3 outcomes max that would make next week a success. More than 3 "top" priorities means none are. For each, name the single first action.
5. Calendarize Match the 3 outcomes to real time blocks against known commitments. Flag over-commitment honestly: if the 3 priorities need 15h and the week has 6h free, say so and cut.
Output template
## Weekly review — week of <date>
### Wins this week
- ...
### Stalled / carried over
- <item> — <why it stalled> → <next action>
### Dropped (consciously)
- ...
### Next week — 3 priorities
1. <outcome> → first action: <verb-first>
2. ...
3. ...
### Time reality check
<Do the 3 priorities fit the free hours? If not, what gets cut or moved.>Rules
- Cap top priorities at 3. Push back if the user lists more.
- Every stalled item leaves the review with a concrete next action or an explicit "dropped".
- Be honest about capacity — an inspiring plan that doesn't fit the week just breeds guilt.
- Don't moralize about the stalled items; name the cause and move on.
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.

