weekly-review
weekly-review is a skill in nano-muse/nanoMuse, last changed 7 Oct 2026. It is instructions only: no scripts, no named hosts and no pre-approved tools. Our pattern check flagged nothing at commit 101d85b on 27 Oct 2026.
Pattern check: nothing flagged · commit 101d85b · 27 Oct 2026
InstallLook 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.
- Licence
- GPL 3.0
- Repo stars
- 2.8k
- Folder last changed
- 7 Oct 2026 (opens in a new tab)
- Publisher
- nano-muse
- Files
- 1 file
- Checked
- 101d85b (opens in a new tab) · 27 Oct 2026
Install
Each tab says whether it installs commit 101d85b, the one we checked, or the latest version.
No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity, and Claude Code for Cline. Kiro needs the folder copied by hand.
Pinned to commit 101d85b, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/nano-muse/nanoMuse.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
git -C "$tmp" sparse-checkout set -- nanomuse/skills/builtin/weekly-review &&
git -C "$tmp" checkout -q 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
mkdir -p .claude/skills &&
mkdir .claude/skills/weekly-review &&
cp -R "$tmp"/nanomuse/skills/builtin/weekly-review/. .claude/skills/weekly-review/ &&
rm -rf "$tmp"If Claude Code was already running and this created the skills folder, run /reload-skills.
Pinned to commit 101d85b, the one we checked.
Skills in the Claude apps belong to your account rather than to a project.
Make weekly-review.zip, with the skill folder at the top level:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/nano-muse/nanoMuse.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
git -C "$tmp" sparse-checkout set -- nanomuse/skills/builtin/weekly-review &&
git -C "$tmp" checkout -q 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
out="$(mktemp -d)" &&
cp -R "$tmp"/nanomuse/skills/builtin/weekly-review "$out"/weekly-review &&
(cd "$out" && zip -qr - weekly-review) > weekly-review.zip &&
rm -rf "$tmp" "$out"In Claude, open Customize > Skills, select +, then + Create skill > Upload a skill, and choose weekly-review.zip.
On Free, Pro and Max plans, turn on Code execution and file creation (Create and edit files in newer settings) under Settings > Capabilities.
Pinned to commit 101d85b, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/nano-muse/nanoMuse.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
git -C "$tmp" sparse-checkout set -- nanomuse/skills/builtin/weekly-review &&
git -C "$tmp" checkout -q 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
mkdir -p .agents/skills &&
mkdir .agents/skills/weekly-review &&
cp -R "$tmp"/nanomuse/skills/builtin/weekly-review/. .agents/skills/weekly-review/ &&
rm -rf "$tmp"Codex picks up new skills on its own; restart it if this one does not appear.
Pinned to commit 101d85b, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/nano-muse/nanoMuse.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
git -C "$tmp" sparse-checkout set -- nanomuse/skills/builtin/weekly-review &&
git -C "$tmp" checkout -q 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
mkdir -p .cursor/skills &&
mkdir .cursor/skills/weekly-review &&
cp -R "$tmp"/nanomuse/skills/builtin/weekly-review/. .cursor/skills/weekly-review/ &&
rm -rf "$tmp"Pinned to commit 101d85b, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/nano-muse/nanoMuse.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
git -C "$tmp" sparse-checkout set -- nanomuse/skills/builtin/weekly-review &&
git -C "$tmp" checkout -q 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
mkdir -p .github/skills &&
mkdir .github/skills/weekly-review &&
cp -R "$tmp"/nanomuse/skills/builtin/weekly-review/. .github/skills/weekly-review/ &&
rm -rf "$tmp"In a running Copilot CLI session, run /skills reload.
Or install it with gh skill, which also installs the commit we checked. Needs GitHub CLI 2.90 or later.
gh skill install nano-muse/nanoMuse nanomuse/skills/builtin/weekly-review/SKILL.md@101d85bcaba632c0fbdd877ea8015f41363bbb62 --agent github-copilot --scope projectPinned to commit 101d85b, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/nano-muse/nanoMuse.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
git -C "$tmp" sparse-checkout set -- nanomuse/skills/builtin/weekly-review &&
git -C "$tmp" checkout -q 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
mkdir -p .gemini/skills &&
mkdir .gemini/skills/weekly-review &&
cp -R "$tmp"/nanomuse/skills/builtin/weekly-review/. .gemini/skills/weekly-review/ &&
rm -rf "$tmp"In a running session, run /skills reload.
Or use Gemini CLI’s own installer. Installs the latest version, not the one we checked.
gemini skills install https://github.com/nano-muse/nanoMuse.git --path nanomuse/skills/builtin/weekly-review --scope workspacePinned to commit 101d85b, the one we checked.
Codex, Cursor, Copilot, VS Code, Gemini CLI, OpenCode, Goose, Amp and Zed all read .agents/skills; Claude Code and Kiro list only their own folders.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/nano-muse/nanoMuse.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
git -C "$tmp" sparse-checkout set -- nanomuse/skills/builtin/weekly-review &&
git -C "$tmp" checkout -q 101d85bcaba632c0fbdd877ea8015f41363bbb62 &&
mkdir -p .agents/skills &&
mkdir .agents/skills/weekly-review &&
cp -R "$tmp"/nanomuse/skills/builtin/weekly-review/. .agents/skills/weekly-review/ &&
rm -rf "$tmp"Or use the skills CLI from skills.sh. Installs the latest version, not the one we checked. The skills CLI reports installs to skills.sh unless you set DISABLE_TELEMETRY=1.
npx skills@1.7.4 add nano-muse/nanoMuse --skill weekly-reviewWhat it can touch
From the files and frontmatter at commit 101d85b. This is how much a skill can do, not whether it is risky.
What it can touch: Instructions only
It is instructions only: no scripts, no named hosts and no pre-approved tools.
Pattern check
Pattern check: nothing flagged · commit 101d85b · 27 Oct 2026
We checked every text file in this skill, at commit 101d85b on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.
Format check
Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.
Agent Skills specFails
The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.
- Error
Line 3: the description value contains a colon followed by a space, which YAML reads as the start of another field. Strict YAML parsers, including the spec's validator, reject the file. F4
Fix: Put the value in quotes, like this: description: 'Look back at the past week and set up the next one: calendar, mail, goals and files i…
- Warning
Fields outside the spec: channel. Uploads to the Claude apps and API, and the spec's validator, reject the file; most agents ignore these fields. O1
Fix: Delete them for a portable skill, or keep them if you only target the agents that read them.
- Note
There is no license field, so readers can't tell whether they may reuse the skill. O2
Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.
- Error
Claude CodePasses
Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.
- Note
Line 3: the description value contains a colon followed by a space, which YAML reads as the start of another field. Claude Code quotes the value itself and loads the skill, but other agents reject it. F4
Fix: Put the value in quotes, like this: description: 'Look back at the past week and set up the next one: calendar, mail, goals and files i…
- Note
Claude Code ignores fields it doesn't know: channel. O1
Fix: Check the spelling against Claude Code's field list, or delete them.
- Note
Claude apps & API uploadFails
Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.
- Error
Line 3: the description value contains a colon followed by a space, which YAML reads as the start of another field. Anthropic's validator rejects it, so packaging and upload fail. F4
Fix: Put the value in quotes, like this: description: 'Look back at the past week and set up the next one: calendar, mail, goals and files i…
- Error
Upload and packaging fail on fields outside the spec: channel. O1
Fix: Delete them, and keep your own data under metadata as text values.
- Note
The description is 220 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4
Fix: If the claude.ai upload refuses it, trim the description to 200 characters.
- Error
OpenAI (Codex & API)Fails
Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.
- Error
Line 3: the description value contains a colon followed by a space, which YAML reads as the start of another field. Codex quotes the value and loads the skill, but OpenAI's upload follows the spec, which needs valid YAML. F4
Fix: Put the value in quotes, like this: description: 'Look back at the past week and set up the next one: calendar, mail, goals and files i…
- Warning
Fields outside the spec: channel. Codex ignores them; OpenAI doesn't say whether its upload accepts them. O1
Fix: Delete them, or move your own data under metadata as text values.
- Error
VS Code & CopilotPasses with warnings
VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.
- Warning
Line 3: the description value contains a colon followed by a space, which YAML reads as the start of another field. VS Code's own YAML reader still loads the skill, but may read some values differently. F4
Fix: Put the value in quotes, like this: description: 'Look back at the past week and set up the next one: calendar, mail, goals and files i…
- Note
VS Code ignores fields it doesn't support: channel. O1
Fix: Delete them unless another agent you target reads them.
- Warning
SKILL.md
We only show SKILL.md text here when its licence clearly allows it.
Read SKILL.md on GitHub (opens in a new tab)Files
1 file
| Path | Size |
|---|---|
| SKILL.md (opens in a new tab) | 2.3 KB |
More from nano-muse/nanoMuse
amap
nano-muse/nanoMuse
Places, routes, travel times, distances and weather in China through the 高德地图 (Amap) MCP server. Use when the user asks how far, how long, how to get somewhere (car, transit, bike, foot), what is near a place, or about the weather in a Chinese city.
- Names web addresses
Pattern check: Nothing flaggedGPL 3.0 · 2.8k repo stars · Updated 7 Oct 2026
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. Use when the user asks which to pick, for a comparison, or "X vs Y".
- Instructions only
Pattern check: Nothing flaggedGPL 3.0 · 2.8k repo stars · Updated 7 Oct 2026
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. Use when the user mentions 飞书, Lark, a 群, a 日程 or a 飞书文档, or wants a colleague told something.
- Runs shell commands
Pattern check: Nothing flaggedGPL 3.0 · 2.8k repo stars · Updated 7 Oct 2026
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. Use when the user asks to triage, sort, catch up on or clear their inbox; never to send anything on its own.
- Instructions only
Pattern check: Nothing flaggedGPL 3.0 · 2.8k repo stars · Updated 7 Oct 2026
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. Use when the user asks 快递到哪了, 什么时候到, 查一下单号, or how much it costs to send something.
- Downloads software
- Reaches the network
- +1 more
Pattern check: Nothing flaggedGPL 3.0 · 2.8k repo stars · Updated 7 Oct 2026
meeting-prep
nano-muse/nanoMuse
Prepare for a meeting (who is in it, what was last said with them, what the user owes them and wants from them) as a one-page brief. Use when the user asks to prepare for or get ready for a meeting, a call or a visit; a trigger can run it before every meeting with a client.
- Instructions only
Pattern check: Nothing flaggedGPL 3.0 · 2.8k repo stars · Updated 7 Oct 2026