minutes-debrief

Solid

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.

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

# /minutes-debrief Post-meeting analysis that reads your latest recording, compares what happened to what you planned, and surfaces decision evolution — so nothing falls through the cracks. ## How it works This is a multi-phase interactive flow. It connects to `/minutes-prep` when a prep file exists, creating a before→after loop. ### Phase 1: Find the most recent recording ```bash minutes list --limit 5 ``` Pick the most recent recording. If there are multiple from today, ask via AskUserQuestion: "You have [N] recordings today. Which one are you debriefing?" with options listing the titles. **If no recent recording exists:** Say: "I don't see any recent recordings. Did you run `minutes record` and `minutes stop`? If the recording is from a specific meeting, tell me the title or date and I'll find it." Don't proceed without a recording to debrief. ### Phase 2: Read the transcript Use `Read` on the meeting file path. Extract from the transcript and frontmatter: - **Decisions made** (from `decisions:` frontmatter or `## Decisions` section) - **Action items created** (from `action_items:` frontmatter or `## Action Items` section) - **Key discussion points** (from `## Summary` or the transcript itself) - **Attendees** (from `attendees:` frontmatter) ### Phase 2b: Check speaker attributions If the meeting has a `speaker_map:` field in frontmatter, check the confidence levels: - **All High confidence**: Speakers are confirmed — use real names throughout the debrief. - ...

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

Data & Documents Listed

meeting-debrief

Extracts structured debriefs from messy meeting notes — decisions, action items, discussion points, and next steps. Use this skill when the user pastes meeting notes, a transcript, bullet points, or any record of a meeting and wants it summarised, organised, or turned into action items. Also triggers when someone asks for a meeting recap, wants to extract decisions from notes, needs to share what happened in a meeting, or says anything like "what did we decide" or "who's doing what." If it looks like meeting content, use this skill.

0 Updated 5 days ago
miniminer-droid
AI & Automation Solid

minutes-recap

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.

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

follow-up

Debrief a meeting and draft the follow-up. Trigger when the user asks to debrief a call, follow up, or "what do I send after that meeting".

8 Updated today
etrebels
AI & Automation Solid

minutes-prep

Interactive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review history with someone before a meeting.

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