weekly-review
Skill7 starsChanged 25 days agoMITView on GitHub
Review the owner's week from available LifeOS records, distinguish current evidence from stale files, and propose changes to priorities or trackers for the owner to choose.
95 other projects use a version of this.
Adopted by
Most recently taken up by
- teodstr/workbenchtheir own version, first seen Nov 15, 2026
- upamune/skillstheir own version, first seen Nov 15, 2026
- odytrice/metaskillstheir own version, first seen Nov 15, 2026
- 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
Used with
Projects with it also use quarterly-review, daily-plan and 9 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
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
TheCraigHewittSkillresearch-brief
Produces a one-page research brief on a topic, person, or company — what they do, what matters, what's changed recently, sources. Use when the user asks to research, look into, brief me on, or get context on a specific topic, company, competitor, or person. Pulls from the web, any project context, and recent emails involving the subject.
Also in 3 projects that use this
Other versions95 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 95
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- chrisblattman/claudeblattman★ 483same 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
85 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- daily-briefSkill
- mission-swapSkill
- quick-captureSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 82 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the owner's identity and enabled modules from dashboard/lifeos.config.json (falling back to dashboard/lifeos.config.example.json).
- Distinctive: line 25
Use *Think once → Build → Measure → Improve* as an optional method, not a judgment of the week.
“Common” is measured: kept by at least 6 in 10 of the 82 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
Offer a manageable review of what happened and what the owner wants next. They choose the depth and whether to change any records; rest, reflection and maintenance are valid outcomes.
Read the owner's identity and enabled modules from dashboard/lifeos.config.json (falling back to dashboard/lifeos.config.example.json); use the area codes there for the areas check.
Steps
- Read
06_Trackers/tasks.md,inbox.md,habits.md,evidence.md, and00_START_HERE.md. The dashboard JSON (dashboard/tasks-data.json,habits-data.json) is first-run seed data. Existing browser tasks/habits can be newer; reconcile a private dashboard export before rewriting the files or claiming the review is complete. Never clear browser storage to force a seed refresh; seedocs/browser-data.md. Note missing tracker files without treating them as empty history. Create one from its template only when file updates are within the owner's request. - Fill a copy of
templates/weekly_review.md(or summarize inline if the owner prefers), filed underreviews/YYYY-Www.md:- Evidence: what actually shipped (artifacts, not intentions) — cross-check
06_Trackers/evidence.md. - Hero mission: did it move toward its gate?
- Areas check: quick 1–5 across the area codes in
dashboard/lifeos.config.json.
- Evidence: what actually shipped (artifacts, not intentions) — cross-check
- Review incomplete work: propose keep, reschedule, park or stop choices. Preserve existing dates and entries until the owner chooses; a review does not automatically roll everything into next week.
- Triage the inbox if wanted: suggest classifications. Keep the original capture or an archive pointer; do not delete entries merely to empty the inbox.
- Choose next steps: offer a focus or several priorities according to the owner's preference. Update trackers and
00_START_HERE.mdonly within the requested editing scope. Runmission-swaponly when they choose a change. - Notion configuration is not send permission. Offer to mirror approved task/habit changes if useful, then follow the owner's explicit authorization. Built-in sync does not mirror weekly reviews; those stay local unless a separate destination and write are authorized.
Rules
- Be honest about wellbeing and relationships, not just output.
- Use Think once → Build → Measure → Improve as an optional method, not a judgment of the week. Do not assign an artifact to compensate for rest or unfinished work.
- The dashboard has one hero slot; the owner decides how many real-life priorities need attention.
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.

