
Weekly Review
Look back at the past week and set up the next one: calendar, mail, goals and files in...
Install
npx skills add nano-muse/nanoMuse --skill weekly-review -g -a claude-code -y- Repository
- nano-muse/nanoMuse3k
- Category
- Engineering
- Updated
- 3d ago
- License
- GPL-3.0
- Context cost
- Lightabout 506 tokens
- Runs scripts
- No, instructions only
What it does
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.
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)
- Calendar:
calendaraction=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:
goalsaction=list; for each active goal,getit and read the notes on steps done this week and the next step. - Mail (only if
read_emailsis 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:
filesaction=list on the workspace; the ones modified this week are what got made. - 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
contactswhen 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.
