agentleFS
Sign inStart free
tograftograf/sidebrain/.claude/skills/weekly-review/SKILL.md

weekly-review

Skill1 starsChanged 5 months agoMITView on GitHub

Week-level review of the vault. Read the week's daily notes and active projects, assess real progress vs. stuck items, give honest feedback, write a weekly note, and plan next week's focus. Use when the user asks for a weekly review / weekly report / "how was my week", or when a week is wrapping up.

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

  • 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

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 82 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:

    Gather the week: Read the last 7+ daily notes in 05-Daily-Notes/, the active project files in 02-Projects/ (status: active), and skim area …

    line 15

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

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

weekly-review — close the week, plan the next

The weekly counterpart to the end-of-day feedback in CLAUDE.md: same honesty, one level up. Vault conventions live in CLAUDE.md.

Folder paths in this skill are the template defaults — the authoritative paths live in the "Folder roles" table in CLAUDE.md's Vault structure section. Look folders up there by role — never trust the literal defaults on a renamed or non-English vault. Write everything in the vault's language.

Steps

  1. Gather the week. Read the last 7+ daily notes in 05-Daily-Notes/, the active project files in 02-Projects/ (status: active), and skim area files touched this week. Note the inbox backlog size.
  2. Assess — real progress, not busyness:
    • Which todos were completed; which are open, and crucially how long they've been open (a todo dragging through five daily notes is a finding, not a footnote).
    • Per active project: did it move? Stalled projects get named.
    • Which areas got attention; which were neglected.
    • Wins worth acknowledging — and whether anything was ingested/learned that should connect to ongoing work.
  3. Give honest feedback in the chat (not in the note) — same tone rules as the end-of-day feedback in CLAUDE.md: volume matches significance, no coaching-speak, name what's stuck, genuinely celebrate real wins.
  4. Write the weekly note to 05-Daily-Notes/YYYY-Www.md (e.g., 2026-W23.md — sorts alongside the daily notes), frontmatter tags: [weekly]. Sections:
    • Highlights — the 2-3 things that defined the week
    • Progress by project — one line each, linked [[wikilinks]]
    • Stuck / overdue — with how long, linked to detail pages
    • Next week's focus — 1-3 priorities, each linked; any new todos obey the two-place todo rule (detail page + today's daily note)
    • Links to the week's daily notes
  5. Offer a vault-lint pass. Weekly is exactly the right lint cadence — one question, run it only on a yes.

Quality bar

  • Ground every statement in the notes — cite via wikilinks; no vague "good progress".
  • The "Next week's focus" must be small (1-3 items). A ten-item focus is a backlog, not a focus.

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