Agent skill

Weekly Review Planning

by NousResearch in NousResearch/hermes-agent

Weekly reset: commitments, stalled work, next-week plan. An agent skill from NousResearch/hermes-agent.

MITAuto-check passedKnowledge Management

Install Weekly Review Planning

skills CLI
$ npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NousResearch/hermes-agent weekly-review-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NousResearch/hermes-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/productivity/weekly-review-planning .claude/skills/weekly-review-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
weekly-review-planning
GitHub stars
252k
Token cost
~994 tokens
SKILL.md length
505 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Weekly reset: commitments, stalled work, next-week plan. An agent skill from NousResearch/hermes-agent.

  • Works in 7 steps: Set systems and window → Review calendar evidence → Clear capture inboxes → …
  • Tasks that involve Journaling and reflection
  • SKILL.md covers When to Use, Procedure, Output Shape and Pitfalls, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Weekly Review Planning is an agent skill from NousResearch/hermes-agent. Weekly reset: commitments, stalled work, next-week plan.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Journaling and reflection and Email management. The repository describes itself as: The agent that grows with you. The licence is MIT.

When your agent uses it

  • Tasks that involve Journaling and reflection
  • Tasks that involve Email management

Example prompts

  • “/weekly-review-planning”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Set systems and window
  2. Review calendar evidence
  3. Clear capture inboxes
  4. Reconcile active projects
  5. Review waiting and commitments
  6. Build a capacity-aware plan
  7. Apply approved updates

What it can do on your machine

Read from SKILL.md and the folder at commit dce1e9b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Weekly Review Planning loads about 994 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 505 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~994

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NousResearch/hermes-agent at commit dce1e9b, republished under its MIT licence (© NousResearch). 505 words, ~994 tokens.

Download SKILL.mdSave it as .claude/skills/weekly-review-planning/SKILL.md (or your agent's skills folder).
name
weekly-review-planning
description
Weekly reset: commitments, stalled work, next-week plan.
version
0.1.0
author
Ben Barclay (benbarclay), Hermes Agent
license
MIT
platforms
linux, macos, windows

Weekly Review and Planning

Run a bounded weekly reset across the user's chosen systems. This is a concrete recurring task, not a generic productivity methodology — the weekly-review Automation Blueprint schedules it as a cron job.

When to Use

  • "Run my weekly review."
  • "What did I commit to and what is slipping?"
  • "Plan next week from my calendar, tasks, and notes."
  • "Find stale projects and waiting items."
  • A cron tick fires for a scheduled weekly review.

Don't use for: daily briefs (see the google-workspace daily-brief reference) or single-inbox triage (email-inbox-triage).

Procedure

1. Set systems and window

Confirm timezone, review period, planning horizon, authoritative task/project store, calendars, inboxes, and allowed writes. Default to recommendations/drafts, not mutations. Done when source-of-truth conflicts have a declared winner.

2. Review calendar evidence

Load google-workspace or the relevant calendar connector. Inspect the completed week for meetings and commitments, then the next 1-2 weeks for deadlines, travel, preparation, and capacity. Capture follow-ups implied by past events and conflicts ahead. Done when both retrospective and horizon are covered.

3. Clear capture inboxes

Review the task inbox, notes (obsidian, notion), flagged email (email-inbox-triage owns thread-level triage), and other declared capture points. Convert each item to next action, project, waiting, scheduled, someday, reference, archive, or delete proposal. Do not mutate until scope is approved. Done when remaining unprocessed items are counted and stated.

4. Reconcile active projects

For each project identify desired outcome, next action, owner, deadline, blocker, last meaningful activity, and source link. Flag projects with no next action, missed dates, duplicate records, or contradictory status. Done when every active project is actionable or explicitly paused.

5. Review waiting and commitments

Find promises made by the user and items owed by others. Propose follow-ups with dates and channels. Do not infer that silence means completion. Done when each waiting item has an owner and next review/follow-up date.

Show full SKILL.md (198 more words)Show less
6. Build a capacity-aware plan

Estimate fixed calendar load and select a small set of weekly outcomes plus near-term next actions. Rank by consequence, deadline, dependency, and effort; do not fill every free hour. Done when the plan fits actual capacity and names deferred work.

7. Apply approved updates

Update tasks/projects, create calendar holds, archive processed items, and draft follow-ups only as approved. Read every changed record back from the provider. Done when verified writes match the review summary.

Output Shape

  1. Wins and completed commitments
  2. Overdue or at risk
  3. Waiting/follow-ups
  4. Stalled or ambiguous projects
  5. Next week's outcomes and calendar constraints
  6. Proposed updates awaiting approval
  7. Coverage gaps

Pitfalls

  • Planning from tasks without calendar capacity.
  • Carrying every unfinished item forward as high priority.
  • Marking projects active with no next action.
  • Silently deleting or rescheduling personal commitments.
  • Treating silence from others as completion.

Verification

  • Both the completed week and the planning horizon were covered, or gaps are stated.
  • Every stalled/waiting flag traces to a specific record, event, or thread.
  • No task, event, or note was mutated without approval; approved writes were read back.
  • The plan names what was deferred, not just what was chosen.

© NousResearch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/productivity/weekly-review-planning of NousResearch/hermes-agent.

Open the folder on GitHubat commit dce1e9b

Compare with similar skills

Weekly Review Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Weekly Review Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Weekly Review Planning this skillNousResearch/hermes-agent252k—~994Automated safety check: PassMIT
Ingestsuperhero-tech/super-brain167—~1.3kAutomated safety check: PassMIT
Em Grid Scorermanager-dot-dev/manager-skills114—~5.8kAutomated safety check: PassMIT
Weekly Reverse Reviewtwhsi/skills259—~1.2kAutomated safety check: PassNone
Oce Field Opsdatadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction345—~532Automated safety check: PassMIT
Journaldavekilleen/Dex494—~1.8kAutomated safety check: PassMIT

Similar skills

  • Ingest

    superhero-tech/super-brain

    Compiles a source from 2-Inbox/ into the wiki, across every page it touches, then archives it.

    167 GitHub stars~1.3k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed
  • Em Grid Scorer

    manager-dot-dev/manager-skills

    Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.

    114 GitHub stars~5.8k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed
  • Reverse weekly review for turning inbox noise, daily plans, diaries, calendars, annual plans, and long-range life plans into one happiness-and-peace-centered weekly plan.

    259 GitHub stars~1.2k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed
  • Oce Field Ops

    datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction

    Field operations in OpenConstructionERP: punch list, daily diary, HSE observations and task tracking on site.

    345 GitHub stars~532 tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed
  • Journal

    davekilleen/Dex

    Toggle journaling or start a morning/evening/weekly journal entry.

    494 GitHub stars~1.8k tokensUpdated yesterday
    Knowledge ManagementAuto-check passed
  • Para Skill

    aiskillstore/marketplace

    PARA method knowledge management for Obsidian vaults. An agent skill from aiskillstore/marketplace.

    433 GitHub stars~2k tokensUpdated yesterday
    Knowledge ManagementAuto-check passed

More from NousResearch/hermes-agent

All 31 skills in this repo
  • AI Presenter Video

    NousResearch/hermes-agent

    Produces a presenter-led video from a topic or script plus one authorized presenter image, with captions, lip-sync checks and acceptance reports.

    253k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Word DOCX Toolkit

    NousResearch/hermes-agent

    Creates, reads, edits and templates Word .docx files with python-docx scripts, including tracked changes, comments, tables of contents and health checks.

    253k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Grounded Citations

    NousResearch/hermes-agent

    Attaches a numbered, URL-backed citation to every outside fact in an answer or document, rejecting quotes that aren't real.

    253k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • PDF

    NousResearch/hermes-agent

    PDF files: create, read, merge, fill, OCR, edit text. An agent skill from NousResearch/hermes-agent.

    253k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Scrollcraft

    NousResearch/hermes-agent

    Premium scroll-driven landing pages; scroll = timeline. An agent skill from NousResearch/hermes-agent.

    253k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • XLSX

    NousResearch/hermes-agent

    Create, read, edit Excel .xlsx workbooks and CSVs. An agent skill from NousResearch/hermes-agent.

    253k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

Questions about Weekly Review Planning

What does Weekly Review Planning do?

Weekly reset: commitments, stalled work, next-week plan. An agent skill from NousResearch/hermes-agent. Weekly Review Planning is an agent skill from NousResearch/hermes-agent. Weekly reset: commitments, stalled work, next-week plan.

When should I use Weekly Review Planning?

Weekly Review Planning fits situations like: tasks that involve Journaling and reflection; tasks that involve Email management.

How do I install Weekly Review Planning in Claude Code?

Run `npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a claude-code`. Or copy the skill folder (skills/productivity/weekly-review-planning in NousResearch/hermes-agent) into .claude/skills/weekly-review-planning in your project. Claude Code loads it when a task matches its description.

How do I install Weekly Review Planning in Codex?

Run `npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a codex`. Or copy the skill folder (skills/productivity/weekly-review-planning in NousResearch/hermes-agent) into .agents/skills/weekly-review-planning in your project. Codex loads it when a task matches its description.

Can I use Weekly Review Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weekly-review-planning, .gemini/skills/weekly-review-planning, .github/skills/weekly-review-planning and .opencode/skills/weekly-review-planning in your project.

What does Weekly Review Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Weekly Review Planning is instructions for the agent only.

Does Weekly Review Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Weekly Review Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Weekly Review Planning use?

Weekly Review Planning is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Weekly Review Planning use?

About 994 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Weekly Review Planning?

Skills that share tags, products or a category with Weekly Review Planning: Ingest (superhero-tech/super-brain, 167 stars), Em Grid Scorer (manager-dot-dev/manager-skills, 114 stars), Weekly Reverse Review (twhsi/skills, 259 stars) and Oce Field Ops (datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction, 345 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Weekly Review Planning?

NousResearch (a GitHub organization) maintains it in NousResearch/hermes-agent, which has 252,350 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 10, 2026.

Source: NousResearch/hermes-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.