- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nano-muse/nanoMuse --skill weekly-review -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nano-muse/nanoMuse --skill weekly-review -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nano-muse/nanoMuse --skill weekly-review -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nano-muse/nanoMuse --skill weekly-review -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/nano-muse/nanoMuse/tree/HEAD/nanomuse/skills/builtin/weekly-reviewFrom the publisher
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.
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.goals action=list; for each active goal, get it and read the notes on steps done this week and the next step.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.files action=list on the workspace; the ones modified this week are what got made.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.
The page has these sections, in this order, with nothing else:
contacts when there is one.Self-contained HTML, inline CSS, readable on a phone, no external resources. Dates as "Mon 3 Mar", not ISO, in the body.
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.
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" o
---name: weekly-reviewdescription: Look back at the past week and set up the next one: calendar, mail, goals and files in one page, with a short…---# nanomuse/skills/builtin/weekly-review/SKILL.mdOverview
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.
FAQ
Download nanomuse/skills/builtin/weekly-review/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/nano-muse/nanoMuse.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.