ops-meeting-minutes
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'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/ops-meeting-minutes”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/ops-meeting-minutesmetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
58 words · 380 chars — "Create structured meeting minutes with decisions, action items, and follow-up tr…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 58 words.
Documentation present and substantive
Documentation present (SKILL.md, 626 words).
Documentation shows usage
Documentation includes 3 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
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
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/ops-meeting-minutes