weekly-review
Skill2 starsChanged 58 days agoMITView on GitHub
Use when the user wants to review their week, plan the next one, or asks "what should I focus on". Pulls from the time log, meeting notes, client updates, and open actions to produce a short review and a focused plan.
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 repository4 other files it gives its agents.
- invoice-generatorSkill
- linkedin-postSkill
- meeting-notes-to-actionsSkill
- setup-businessSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 80 edited versions we read keep these.
6
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
Only two, and only if not answerable from files:
- Distinctive: line 59
Every "Stuck" item gets a smallest-next-step, never just a complaint.
- Distinctive: line 60
Keep it under a page.
- Distinctive: line 63
Do not moralize about productivity.
- Distinctive: line 64
Do not carry forward more than 5 items — force choices.
- Distinctive: line 65
Do not invent activity for days with no data.
“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
Fifteen minutes on Friday that make Monday easy. Look back at what actually happened, look forward at what matters, and surface what's stuck.
Step 1 — Gather (read what exists, skip what doesn't)
logs/time-log.md— hours by client this week.meetings/*.mdfrom this week — open actions with owner "Me" and any unresolved open questions.projects/*/updates/— this week's client updates: promised "next week" items.invoices/— anything overdue.leads/,outreach/— prospects awaiting follow-up (check follow-up schedules).- Last week's review in
reviews/— the plan you're checking against. .solo/business.md— active clients, to spot anyone who got zero attention.
Step 2 — Ask two questions
Only two, and only if not answerable from files:
- "Anything that happened this week that isn't in the files?"
- "What's the one thing next week has to deliver?"
Step 3 — Write
reviews/<YYYY-MM-DD>.md:
# Week of <Mon date> — review
## What happened
- Hours: <total> (<client: h>, <client: h>)
- Delivered: <bullets, from updates/meetings>
- Won / lost / pipeline: <proposals sent, replies, new leads>
## Plan vs. reality
<Last week's plan items with ✅ done / ➡️ carried / ❌ dropped, one line each. Skip if no previous review.>
## Stuck
- <item> — <why> — <the smallest next step>
## Money
- Overdue: <invoices or "none"> · Unbilled: <hours/value or "none">
## Next week
**Must:** <the one thing>
**Should:** <2–3 items>
**Could:** <parking lot>
## Client check
<Any active client with no contact in 7+ days → "Send a note to X.">
## One observation
<A single honest sentence about the week — pattern, energy, risk. No pep talk.>Rules
- Facts from files first; the user's answers fill gaps.
- "Must" is exactly one item. If the user gives three, ask which one.
- Every "Stuck" item gets a smallest-next-step, never just a complaint.
- Keep it under a page.
Do not
- Do not moralize about productivity.
- Do not carry forward more than 5 items — force choices.
- Do not invent activity for days with no data; say "no data logged".
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.

