Agent skill · Code Review & Quality

minutes-weekly

Weekly meeting synthesis — themes, decision arcs, stale commitments, and what deserves your attention next week. Use when the user says "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", or at the end of a work week.

silversteingithub.com/silversteinGitHub ↗
claude-codeMIT
Install
npx skills add silverstein/minutes --skill minutes-weekly --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Requires: opencode
Path: .opencode/skills/minutes-weekly/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,410
Language: Rust

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-weekly" ``` # /minutes-weekly Synthesize a week of policy-authorized normal meetings and voice memos into a forward-looking brief — themes, decision arcs, stale commitments, and what deserves attention Monday. Restricted history is excluded by default. ## How it works This is a synthesis skill, not a command wrapper. It reads across the normal meetings authorized by Minutes, cross-references decisions and action items, and produces an intelligence brief. Restricted meetings are excluded from this agent workflow by default and must never be treated as absent facts. ### Phase 1: Gather this week's recordings ```bash minutes list --limit 50 ``` Filter to recordings from the last 7 days by checking the `date` field in each result's frontmatter. Do NOT use `minutes search` with a date string as the query — that searches file content, not dates. For each selected recording, run `minutes get "<exact path>" --json`, require exit status 0, and use only the returned conten

What's inside
Steps it walks through
  1. Skill Path
  2. How it works
  3. Phase 1: Gather this week's recordings
  4. Phase 2: Theme extraction
  5. Phase 3: Decision evolution arcs
  6. Phase 4: Action item audit
  7. Phase 4b: Relationship intelligence
  8. Phase 5: Unresolved preps
  9. Phase 6: Forward brief
  10. Phase 7: Closing ritual
  11. Gotchas
Commands it runs
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills"
export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-weekly"
minutes list --limit 50
minutes search "<topic>" --since <30-days-ago> --limit 20
minutes actions
ls ~/.minutes/preps/ 2>/dev/null
node "$MINUTES_SKILLS_ROOT/_runtime/hooks/lib/minutes-learn-cli.mjs" get-presentation-focus weekly
More from minutes
All skills →
About this skill
What does the minutes-weekly skill do?

Weekly meeting synthesis — themes, decision arcs, stale commitments, and what deserves your attention next week. Use when the user says "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", or at the end of a work week.

How do I install it?

Run `npx skills add silverstein/minutes --skill minutes-weekly --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From silverstein/minutes, a repository with 1,410 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going