New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Weekly Review

by nano-muse in nano-muse/nanoMuse

Look back at the past week and set up the next one: calendar, mail, goals and files in one page, with a short plan.

GPL-3.0Auto-check passedKnowledge Management

Install Weekly Review

skills CLI
$ npx skills add nano-muse/nanoMuse --skill weekly-review -a claude-code

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

GitHub CLI
$ gh skill install nano-muse/nanoMuse weekly-review --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/nano-muse/nanoMuse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/nanomuse/skills/builtin/weekly-review .claude/skills/weekly-review && 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
GitHub stars
813
Token cost
~587 tokens
SKILL.md length
335 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
GPL-3.0

At a glance

Look back at the past week and set up the next one: calendar, mail, goals and files in one page, with a short plan.

  • Works in 5 steps: Calendar: calendar action=agenda for the… → Goals: goals action=list; for each… → Mail (only if read_emails is available):… → …
  • The user asks for a weekly review
  • SKILL.md covers Gather (all read-only), Write and Finish
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Weekly Review is an agent skill from nano-muse/nanoMuse. Look back at the past week and set up the next one: calendar, mail, goals and files in one page, with a short plan. Use when the user asks for a weekly review, a week in review, "how did my week go" or to plan next week.

Its SKILL.md is about 590 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. The repository describes itself as: nanoMuse: an open-source personal agent for every device you own. One agent with a name and a look of its own that does things, keeps working while the app is closed, remembers… The licence is GPL-3.0.

When your agent uses it

  • The user asks for a weekly review
  • A week in review
  • How did my week go

Example prompts

  • “how did my week go”
  • “/weekly-review”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Calendar: calendar action=agenda for the past 7 days, then for the next 7. Note what took the most time, what repeats, and anything next…
  2. Goals: goals action=list; for each active goal, get it and read the notes on steps done this week and the next step.
  3. Mail (only if read_emails is available): the last 7 days, unread_only=false; look for threads that are waiting on the user and threads the…
  4. Files: files action=list on the workspace; the ones modified this week are what got made.
  5. Memory: recall "weekly review" for how the user liked past reviews (length, tone, what to leave out).

What it can do on your machine

Read from SKILL.md and the folder at commit 5379e97. 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 loads about 587 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 335 words of instructions outside code blocks.

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

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 nano-muse/nanoMuse at commit 5379e97, republished under its GPL-3.0 licence (© nano-muse). 335 words, ~587 tokens.

Download SKILL.mdSave it as .claude/skills/weekly-review/SKILL.md (or your agent's skills folder).
name
weekly-review
description
Look back at the past week and set up the next one: calendar, mail, goals and files in one page, with a short plan. Use when the user asks for a weekly review, a week in review, "how did my week go" or to plan next week.
channel
mixed
metadata
author: nanoMuse version: "1"

Weekly review

One page, reviews/YYYY-Www.html in the workspace (ISO week), and a five-line summary in chat. Overwrite the page if it exists for the same week.

Gather (all read-only)

  1. Calendar: calendar action=agenda for the past 7 days, then for the next 7. Note what took the most time, what repeats, and anything next week that needs preparing.
  2. Goals: goals action=list; for each active goal, get it and read the notes on steps done this week and the next step.
  3. Mail (only if read_emails is available): the last 7 days, unread_only=false; look for threads that are waiting on the user and threads the user is waiting on. Never quote a whole mail; a line per thread is enough.
  4. Files: files action=list on the workspace; the ones modified this week are what got made.
  5. Memory: recall "weekly review" for how the user liked past reviews (length, tone, what to leave out).

Do not ask the user questions before gathering. Missing connectors are not a problem: leave that section out and say so in one line.

Write

The page has these sections, in this order, with nothing else:

  • The week in one line.
  • Done: what got finished (goal steps, files made, meetings that mattered). Bullet points, past tense, no praise.
  • Still open: waiting on the user / waiting on others, with the person's name from contacts when there is one.
  • Next week: the calendar's fixed points, then the two or three things that would matter most, as checkboxes. Prefer the goals' next steps.
  • Goals: one line per goal, progress and the next step; flag anything overdue.

Self-contained HTML, inline CSS, readable on a phone, no external resources. Dates as "Mon 3 Mar", not ISO, in the body.

Finish

Reply with the one-line summary, the three "next week" items, and the page's name. Then ask one question at most, usually whether to turn the "next week" items into a goal or reminders. If the user says the review should be different next time, remember that.

© nano-muse, GPL-3.0. 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 nanomuse/skills/builtin/weekly-review of nano-muse/nanoMuse.

Open the folder on GitHubat commit 5379e97

Compare with similar skills

Weekly Review 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Weekly Review this skillnano-muse/nanoMuse813—~587Automated safety check: PassGPL-3.0
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
Munger Perspectivealchaincyf/munger-skill3791 repos~3.7kAutomated safety check: PassMIT
Daily Journalhuytieu/COG-second-brain1.3k—~1.3kAutomated safety check: PassMIT
Letterboxd Diaryjoe-bell/skills211—~4.2kAutomated safety check: PassMIT
Em Grid Scorermanager-dot-dev/manager-skills114—~5.8kAutomated safety check: PassMIT

Similar skills

  • LLM Wiki

    lewislulu/llm-wiki-skill

    Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • Munger Perspective

    alchaincyf/munger-skill

    查理·芒格的思维框架与表达方式。基于《穷查理宝典》、伯克希尔/Daily Journal股东会、 USC/哈佛演讲、访谈记录、外部批评等50+来源的深度调研， 提炼5个核心心智模型、8条决策启发式和完整的表达DNA。

    379 GitHub starsUsed in 1 repo~3.7k tokens
    Knowledge ManagementAuto-check passed

  • Daily Journal

    huytieu/COG-second-brain

    A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.

    1.3k GitHub stars~1.3k tokensUpdated 8 days ago
    Knowledge ManagementAuto-check passed

  • Letterboxd Diary

    joe-bell/skills

    Fetch recently watched films from a Letterboxd member's diary RSS feed and render them as a compact markdown list, with first-run setup for the username.

    211 GitHub stars~4.2k tokensUpdated 3 days 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

  • Digital Brain

    foryourhealth111-pixel/Vibe-Skills

    This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content…

    3.6k GitHub stars~1.7k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

More from nano-muse/nanoMuse

All 11 skills in this repo

  • Amap

    nano-muse/nanoMuse

    Places, routes, travel times, distances and weather in China through the 高德地图 (Amap) MCP server.

    813 GitHub stars~964 tokensUpdated today
    Auto-check passed

  • Kuaidi100

    nano-muse/nanoMuse

    Where a parcel is, when it will arrive and what a shipment would cost, through the 快递100 MCP server: any Chinese courier (顺丰, 京东, 中通, 圆通, 韵达, 邮政 and more) from a tracking number.

    813 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Train Tickets

    nano-muse/nanoMuse

    Trains in China through the 12306 MCP server: routes, dates, options, connections and stops with no screen; booking only on the user's word, in the 12306 app on their phone, stopping before payment.

    813 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Compare Options

    nano-muse/nanoMuse

    Compare two to five options (products, plans, places, tools, offers) on the criteria that matter to the user, in a table the user can re-weight, with a recommendation.

    813 GitHub stars~588 tokensUpdated today
    Auto-check passed

  • Feishu

    nano-muse/nanoMuse

    The user's 飞书 / Lark through its command-line tool (lark-cli): agenda, people and groups, reading and sending messages, events, tasks, documents, with no app open.

    813 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Inbox Triage

    nano-muse/nanoMuse

    Go through recent mail and sort it into needs-a-reply, waiting-on-others, to-do and can-ignore, with draft replies ready for review.

    813 GitHub stars~597 tokensUpdated today
    Auto-check passed

Categories

Questions about Weekly Review

What does Weekly Review do?

Look back at the past week and set up the next one: calendar, mail, goals and files in one page, with a short plan. Weekly Review is an agent skill from nano-muse/nanoMuse. Look back at the past week and set up the next one: calendar, mail, goals and files in one page, with a short plan.

When should I use Weekly Review?

Weekly Review fits situations like: the user asks for a weekly review; A week in review; how did my week go.

How do I install Weekly Review in Claude Code?

Run `npx skills add nano-muse/nanoMuse --skill weekly-review -a claude-code`. Or copy the skill folder (nanomuse/skills/builtin/weekly-review in nano-muse/nanoMuse) into .claude/skills/weekly-review in your project. Claude Code loads it when a task matches its description.

How do I install Weekly Review in Codex?

Run `npx skills add nano-muse/nanoMuse --skill weekly-review -a codex`. Or copy the skill folder (nanomuse/skills/builtin/weekly-review in nano-muse/nanoMuse) into .agents/skills/weekly-review in your project. Codex loads it when a task matches its description.

Can I use Weekly Review 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 nano-muse/nanoMuse --skill weekly-review -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, .gemini/skills/weekly-review, .github/skills/weekly-review and .opencode/skills/weekly-review in your project.

What does Weekly Review need to run?

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

Does Weekly Review 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 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 use?

Weekly Review is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Weekly Review use?

About 587 tokens (SKILL.md is roughly 2.3k 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?

Skills that share tags, products or a category with Weekly Review: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 379 stars), Daily Journal (huytieu/COG-second-brain, 1.3k stars) and Letterboxd Diary (joe-bell/skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Weekly Review?

nano-muse (a GitHub organization) maintains it in nano-muse/nanoMuse, which has 813 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 11, 2026.

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