agentleFS
chacosoldierchacosoldier/compabob/.claude/skills/weekly-review/SKILL.md

weekly-review

Skill34 starsChanged 24 days agoMITView on GitHub

End-of-week review: what got done, what slipped, decisions made, and next week's top 3 priorities. Use for \"/weekly-review\", \"end-of-week review\", \"what happened this week\", or on the last working day of the week.

99 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

  • seedprodSkill

    daily-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-skillsSkill

    meeting-notes

    >

    Also in 8 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, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 0

    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
  1. Very specific:

    If meeting notes exist in vault/, scan recent ones for open action items.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 85 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

Produce a terse end-of-week summary that captures what changed and what is still owed.

Steps

  1. Determine the Week. Confirm the ISO week (e.g. 2026-W21). Use date or the inject-now hook.
  2. Gather inputs. Read:
    • vault/Daily/: all daily notes from Monday through today (or the last 7 days). Pull ## Priorities, ## Completed, and any ## Reflection sections.
    • vault/Decisions/: any decision records dated this week.
    • memory/topics/: entries modified this week (check memory/MEMORY.md for the index).
    • If meeting notes exist in vault/, scan recent ones for open action items.
  3. Synthesize five sections:

    • Done: what was completed (shipped, merged, decided, closed).
    • Slipped: what was planned but not done; carry-forward items.
    • Decisions: key decisions made (link to vault/Decisions/ files).
    • Owed to others: commitments the user owes to someone else.
    • Owed to self: commitments the user made to themselves.
  4. Propose top 3 priorities for next week. Base them on the slip-list and the most consequential pending commitments. One sentence each.
  5. Write to vault (optional). Ask the user; if they approve, write to vault/Weekly/YYYY-WW.md.

Output

Lead with one sentence summarising the week. Then:

## Weekly Review: YYYY-WW

**Done**
- ...

**Slipped**
- ...

**Decisions**
- ...

**Owed to others**
- ...

**Owed to self**
- ...

### Next week's top 3
1. ...
2. ...
3. ...

Terse and scannable. Omit any empty section. End with no closing line.

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.