minutes-recap

Solid

Generate a daily digest of today's meetings and voice memos — key decisions, action items, and themes across all 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.

AI & Automation 1,239 stars 131 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.agents/skills/minutes" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-recap" ``` # /minutes-recap Synthesize all of today's meetings and voice memos into a single daily brief. ## How to generate the recap 1. **Find today's recordings** using the `/minutes-search` skill: ```bash minutes search "$(date +%Y-%m-%d)" --limit 50 ``` 2. **Read each meeting file** using `Read` on the paths returned 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 recap - **Cross-reference** across meetings: if pricing came up in two different calls, note that - **Surface conflicts**: if Meeting A decided X but Meeting B discussed doing Y, flag it - **Prioritize action items**: these are the things the user needs to act on - **Include voice memos**: ideas captured on the go are easy to forget — surface them - If there are no meetings or memos today, say so clearly rather than making something up ## Interactive conflict detection When you find conflicts between meetings (e.g., different decisions on the same topic, contradictory action items, or shifted priorities), don't just note them ...

Details

Author
silverstein
Repository
silverstein/minutes
Created
2 months ago
Last Updated
2 days ago
Language
Rust
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

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.

1,239 Updated 2 days ago
silverstein
AI & Automation Solid

minutes-record

Start or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.

1,239 Updated 2 days ago
silverstein
AI & Automation Solid

minutes-brief

Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

1,239 Updated 2 days ago
silverstein
AI & Automation Solid

meeting-minutes

Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.

34,158 Updated yesterday
github
AI & Automation Solid

minutes-debrief

Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.

1,239 Updated 2 days ago
silverstein