agentleFS
Sign inStart free
QuixiAIQuixiAI/Hexis/skills/installed/weekly-review/SKILL.md

weekly-review

Skill623 starsChanged 10 months agoMITView on GitHub

Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

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

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 79 edited versions we read keep these.

  • 3

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

    Create an evidence-based review of what happened, what remains open, and what deserves attention next.

    line 14
  2. Very specific:

    If the user asks to include GitHub work, activate github-issues when configured rather than guessing from local memories.

    line 28
  3. Distinctive:

    Never complete, delete, reprioritize, or reschedule work merely because it looks stale.

    line 33
  4. Distinctive:

    Never read the permanent journal by default.

    line 34

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

Create an evidence-based review of what happened, what remains open, and what deserves attention next. The review should help the user decide; it should not silently rewrite their systems.

Workflow

  1. Fix the window. State the date range and time zone. Default to the current calendar week through today, and adjust when the user means a rolling seven days or a different work week.
  2. Collect evidence. List goals and backlog items, recall recent outcomes and commitments, and inspect relevant calendar events. Search email only for targeted open loops; do not turn a review into an inbox crawl. Read journal entries only when the user asks to include the journal.
  3. Reconcile planned and actual. For each active goal, distinguish completed evidence, progress, blockers, stale assumptions, and work that merely remained scheduled. Do not count an event or sent message as success without supporting context.
  4. Surface the week. Summarize wins, decisions, missed or moved commitments, unresolved conversations, workload patterns, and lessons. Keep facts separate from interpretations.
  5. Propose next week. Recommend a small set of priorities, concrete next actions, calendar pressure points, and items to defer or drop. Explain the tradeoff behind each recommendation.
  6. Let the user choose. Present proposed goal changes, task completions, new tasks, and journal or memory writes as a reviewable plan. Apply only the items the user selects, in the destination they select.
  7. Close the loop. Report the final decisions and remaining unknowns. If requested, store a concise review with the date window and source attribution.

Optional Integrations

  • If the user asks to include GitHub work, activate github-issues when configured rather than guessing from local memories.
  • Todoist and Asana may enrich task coverage when their plugins are enabled. Their absence must not block a review based on Hexis goals and backlog.

Control and Failure Boundaries

  • Never complete, delete, reprioritize, or reschedule work merely because it looks stale; each mutation needs an explicit user choice.
  • Never read the permanent journal by default; it is a deliberate source, not passive context.
  • Missing integrations reduce coverage, not honesty. State which sources were checked and continue with what is available.

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