agentleFS
Sign inStart free
Itsme23476Itsme23476/everyday-claude-skills/weekly-review/SKILL.md

weekly-review

Skill1 starsChanged 3 months agoMITView on GitHub

Run a short end-of-week review — what got done, what slipped, and the three things that matter most next week — pulled from the user's calendar, tasks and notes. Use when the user says "weekly review", "wrap up my week", "plan next week", or "how did this week go".

92 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 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.
  • 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

  • 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

  • zephyrwang6Skill

    daily-review

    每日工作回顾与洞察分析，对用户前一天的对话历史和使用数据进行总结与建议

    Also in 3 projects that use this

  • TheCraigHewittSkill

    research-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

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 1

    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
  1. Distinctive:

    Don't reschedule the calendar or close tasks yourself — propose, the user decides.

    line 50

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly Review

Ten minutes that make the next week calmer. Reflection, then a short plan.

Look back (read-only)

  • Calendar — what actually happened this week; meetings that ate the day.
  • Tasks — what got done, what's still open, what's been open too long.
  • Notes — anything captured this week that needs a next step.

Reflect

Answer three questions, briefly and honestly:

  1. What moved forward this week that actually mattered?
  2. What slipped — and is it dead, or just delayed?
  3. What kept interrupting the important work?

Plan next week

Pick three priorities. Not ten. If everything's a priority, nothing is. For each, name the first concrete action. Then glance at next week's calendar and say where those three will realistically fit — or warn that they won't.

Deliver

THIS WEEK
  Shipped: the newsletter, the client proposal
  Slipped: the tax return (delayed, not dead) — do it Monday
  Drag:    back-to-back meetings Tue/Wed killed deep work

NEXT WEEK — top 3
  1. Finish the tax return        → first action: gather receipts
  2. Record the tutorial          → needs a clear morning; Thursday's open
  3. Reply to the three warm leads → 30 min, Monday

Heads-up: Wednesday's fully booked. Don't plan real work there.

Rules

  • Be honest, not harsh. Name what slipped without a lecture.
  • Three priorities, maximum. Push back if the user tries to add a fourth.
  • Don't reschedule the calendar or close tasks yourself — propose, the user decides.

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.

Check your setup, free