weekly-review skillA
weekly-review is agent-read markdown (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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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.** …
Read the whole file at its exact version.
How to install
mdr add nano-muse/nanomuse/weekly-review@v1mdr add nano-muse/nanomuse/weekly-review@sha256:479951d8caf1229bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_x7bai7lthnjxegzs)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2363 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nano-muse/nanomuse · 6 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_x7bai7lthnjxegzs GET https://markdownregistry.com/api/v1/resolve?ref=nano-muse/nanomuse/weekly-review GET https://markdownregistry.com/api/v1/blob/479951d8caf1229bb1753e3cf6221dc7b3cd7f79f916eaa627f21327bd2720d3
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from nano-muse/nanomuse
Every file in nano-muse/nanomuse