agentleFS
marinvchmarinvch/Cortex/skills/weekly-review/SKILL.md

weekly-review

Skill1 starsChanged 18 days agoMITView on GitHub

Weekly vault maintenance — empty the inbox, update projects, restamp current-focus, archive what is stale.

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

  • 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

  • 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

Files
SKILL.md

/weekly-review — keep the brain clean

A vault rots without this. Walk the user through it; act only on confirmation.

Step 1 — Empty the inbox

For each item in inbox/ (and ## 💡 Captured in recent daily notes), route it to exactly one:

  • Trash — delete.
  • Note — durable insight → rewrite as an atomic note in notes/ (from templates/note.md), linked to related notes. This is the high-value step.
  • Action → into a projects/ or areas/ note as a - [ ].
  • Resource → file under resources/. Goal: inbox/ empty (or close) by the end.

Step 2 — Update projects

For each file in projects/: still active? Update ## Next actions. If done, set status: done and move to archives/. If stalled with no next action, either define one or park it in archives/.

Step 3 — Review areas

Skim areas/*: are you holding the standard you set? Note anything slipping.

Step 4 — Restamp focus

Rewrite context/current-focus.md for the coming week (this week / blocked / parked). Stamp today.

Step 5 — Capture decisions

Append any decisions made during review to decisions/log.md.

Close

One-line summary: items processed, notes created, projects closed, focus updated. Suggest running /audit-notes score if it's been a week, or /retrospective if it's been two.

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.