agentleFS
Rome-1Rome-1/obsidian-claude-starter/.claude/skills/weekly-review/SKILL.md

weekly-review

Skill5 starsChanged 34 days agoMITView on GitHub

Drafts a weekly review in Journal/ from what actually changed in the vault this week (git history, notes updated, meetings held), every unchecked action item, stale active projects, people with overdue follow-ups, inbox leftovers and open feedback-log entries; then helps the user pick next week's focus. Use when the user says "weekly review", "review my week", "what did I do this week", "what's open", "plan next week", or runs /weekly-review.

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

  • 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

  • JerovinoSkill

    process-inbox

    Processes tasks.md inbox items by triaging each one to its proper location in the vault

    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

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default window: the last 7 days.

    line 12
  2. Very specific:

    Create Journal/YYYY-Www-Review.md (ISO week, e.g.

    line 28
  3. Distinctive:

    Next week's focus: leave for the user; suggest two or three candidates based on the open loops.

    line 33
  4. Very specific:

    If the inbox is not empty, offer /inbox-triage.

    line 45

“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

Build the draft from evidence in the vault, then let the user edit it. Do not invent accomplishments.

1. Collect

Default window: the last 7 days. Use these sources, and say in the draft which ones you used:

  • Changes: git log --since="7 days ago" --name-only --format="%ad %s" --date=short if the vault is a git repo; otherwise notes whose updated: falls in the window.
  • Meetings: notes in Meetings/ dated in the window.
  • Open action items: unchecked boxes across the vault, excluding templates and examples: grep -rnE --include="*.md" --exclude-dir=".*" "^[[:space:]]*- \[ \]" . | grep -v -e "System/Templates" -e "_examples"
  • Stale projects: status: active with updated: older than 30 days.
  • People: next_action set and last_contact older than 30 days.
  • Inbox: files in Inbox/ other than README.md.
  • Feedback: lines in System/agent-feedback.md still marked [status: open].
  • Beads (only if .beads/ exists): bd ready and anything closed this week.

A count of zero is a finding only if the search could have found something; if a source was unavailable (no git, no beads), say so instead of reporting zero.

2. Draft

Create Journal/YYYY-Www-Review.md (ISO week, e.g. 2026-W03) from System/Templates/Weekly-Review.md:

  • What happened: the main things, grouped by project, with links. Short.
  • Projects: one line per active project: moved, stalled, or done.
  • Open loops: action items grouped by project, stale projects, overdue follow-ups, inbox count.
  • Next week's focus: leave for the user; suggest two or three candidates based on the open loops.
  • Notes on the system: open feedback entries, plus anything you noticed (a template field nobody fills, a skill that did not fit).

3. Review with the user

Show the open loops and ask, in one message:

  • Which items are done, dropped, or still on? (Check off or remove them in their source notes, not only in the review.)
  • Which stale projects should be paused or archived? (Set status: paused, or move to Archive/, with a yes.)
  • What are next week's two or three priorities?

Then fill in the focus section, set updated: on notes you changed, run python3 scripts/check_vault.py, and commit if the user agreed to agent commits. If the inbox is not empty, offer /inbox-triage. If feedback entries are open, offer /log-feedback to work through them.

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.