Skip to content
FunCoding

Search

Search docs, Skills and MCP

weekly-review

运维与云558nanomuse/skills/builtin/weekly-review/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/nano-muse/nanomuse/weekly-review/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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.

Similar Skills

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

Ops & cloud

shipping-and-launch
addyosmani/agent-skills104k

shipping-and-launch

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Ops & cloud

observability-and-instrumentation
addyosmani/agent-skills104k

observability-and-instrumentation

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

Ops & cloud

internal-comms
ComposioHQ/awesome-claude-skills77k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

Ops & cloud

vercel-react-best-practices
CherryHQ/cherry-studio52k

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Ops & cloud

acceptance-orchestrator
sickn33/agentic-awesome-skills47k

acceptance-orchestrator

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

Ops & cloud