Ops Meeting Minutes Skill for Claude
Create structured meeting minutes with decisions, action items, and follow-up tracking. Use this skill when the user needs to document meetings effectively, track action items, improve meeting productivity, or set up a meeting note system — even if they say 'take notes for this meeting', 'what was decided', 'who's responsible for what', or 'our meetings have no follow-through'.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/asgard-ai-platform/skills --skill ops-meeting-minutesWhat comes with it
15 244 bytes besides the instructionThe instruction itself
9 sections, as written by the authorMeeting Minutes
Framework
IRON LAW: Every Meeting Must Produce Decisions + Action Items
If a meeting ends with no documented decisions and no action items with
owners and deadlines, the meeting was a waste of time. Capture these
DURING the meeting, not after. Minutes without action items are a diary.
Meeting Minutes Template
# Meeting: {Title}
Date: {YYYY-MM-DD} | Time: {HH:MM-HH:MM} | Location: {room/link}
Attendees: {names}
Absent: {names}
Facilitator: {name} | Note-taker: {name}
## Agenda
1. {topic 1} — {presenter} ({X min})
2. {topic 2} — {presenter} ({X min})
3. {topic 3} — {presenter} ({X min})
## Discussion Notes
### {Topic 1}
- {Key point discussed}
- {Different viewpoints raised}
- **DECISION**: {what was decided}
### {Topic 2}
- {Key point}
- **DECISION**: {what was decided} / **DEFERRED**: {to when/what condition}
## Action Items
| # | Action | Owner | Deadline | Status |
|---|--------|-------|----------|--------|
| 1 | {specific task} | {name} | {date} | Open |
| 2 | {specific task} | {name} | {date} | Open |
## Next Meeting
- Date: {next meeting date}
- Agenda items for next time: {carry-over items}
Action Item Format: WHO + WHAT + WHEN
Bad: "Follow up on the pricing issue"
Good: "@Sarah to prepare pricing comparison table with 3 competitors by April 10"
Meeting Efficiency Tips
- Agenda first: Distribute agenda 24+ hours before the meeting
- Time-box: Assign time limits per topic. Use a visible timer.
- Parking lot: Off-topic items go to a "parking lot" list for later — don't derail the meeting
- Last 5 minutes: Reserve for summarizing decisions and action items
- Distribute within 24 hours: Send minutes the same day or next morning while memory is fresh
AI Meeting Tools
| Tool | Capability | Best For |
|------|-----------|----------|
| Otter.ai | Transcription + summary | English meetings |
| Fireflies.ai | Transcription + action item extraction | Team meetings |
| Claude/GPT | Summarize transcript, extract decisions | Post-meeting processing |
| Notion AI | In-context meeting notes | Notion-based teams |
Even with AI transcription, a human note-taker should capture DECISIONS and ACTION ITEMS in real-time. AI captures what was said; humans capture what was DECIDED.
Output Format
# Meeting Minutes: {Title} — {Date}
## Decisions Made
1. {decision + context}
2. {decision}
## Action Items
| # | Action | Owner | Deadline |
|---|--------|-------|----------|
| 1 | {task} | {name} | {date} |
## Key Discussion Points
- {summary of important discussion, not verbatim}
## Parking Lot (for future discussion)
- {deferred topic}
Gotchas
- Minutes ≠ transcript: Don't capture everything said. Capture: decisions, action items, key disagreements, and context needed to understand decisions later.
- Action items without deadlines don't get done: "ASAP" is not a deadline. Every action item needs a specific date.
- The note-taker has power: They decide what's recorded as a "decision." Assign this role intentionally.
- Follow up on action items: Minutes sent without follow-up are ignored. Review action item status at the START of the next meeting.
- Recurring meetings need structure: Weekly standups, monthly reviews, and quarterly planning each need different minute formats. One size doesn't fit all.
References
- For meeting facilitation techniques, see
references/facilitation.md
Other skills for the same job
different authors, same section of the catalogue
Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack.
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
How to use it
Take asgard-ai-platform/ops-meeting-minutes from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.