Agent skill

minutes-recap

Generate a daily digest of today's policy-authorized meetings and voice memos — key decisions, action items, and themes across available recordings. Use when the user asks "recap my day", "what happened in my meetings today", "daily summary", "what did I discuss today", "any action items from today", or wants a consolidated view of the day's conversations.

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

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

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Requires: opencode
Path: .opencode/skills/minutes-recap/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-recap" ``` # /minutes-recap Synthesize today's policy-authorized normal meetings and voice memos into a single daily brief. Restricted history is excluded from this agent workflow by default and must never be treated as absent evidence. ## How to generate the recap 1. **Find today's recordings** from the bounded live list: ```bash minutes list --limit 50 ``` Require exit status 0, parse the JSON written to stdout, and select entries whose `date` is today. A date string is not a search query. 2. **Read each selected recording** with `minutes get "<exact path>" --json`. Require exit status 0 and use only the returned content. Never reopen list paths through the host filesystem. 3. **Synthesize into a daily brief** — use the template in `templates/daily-recap.md` as a starting point, adapting sections based on what actually exists in the day's recordings. 4. Present the recap directly in the conversation — don't save it to a file unless asked. ## What makes a good r

What's inside
Steps it walks through
  1. Skill Path
  2. How to generate the recap
  3. What makes a good recap
  4. Interactive conflict detection
  5. Gotchas
Ships with 1 file
  • templates/daily-recap.md
Commands it runs
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills"
export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-recap"
minutes list --limit 50
More from minutes
All skills →
About this skill
What does the minutes-recap skill do?

Generate a daily digest of today's policy-authorized meetings and voice memos — key decisions, action items, and themes across available recordings. Use when the user asks "recap my day", "what happened in my meetings today", "daily summary", "what did I discuss today", "any action items from today", or wants a consolidated view of the day's conversations.

How do I install it?

Run `npx skills add silverstein/minutes --skill minutes-recap --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