Meeting Notes
Turn messy call transcripts or bullet scribbles into structured minutes with decisions, owners, and deadlines.
Overview
meeting-notes is an agent skill most often used in Build (pm) (also Grow, support; Operate, iterate) that produces structured meeting summaries with decisions and assigned action items.
Install
npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill meeting-notesWhat is this skill?
- Fixed markdown template: agenda, discussion by topic, decisions, action-item table, parking lot
- Action items require owner, deadline, and checkbox status columns
- Best practices: capture themes not verbatim, send notes within 24 hours
- Supports team syncs, stakeholder reviews, and async decision logs
- Trigger phrases: meeting notes, minutes, action items, structured documentation
Adoption & trust: 2.4k installs on skills.sh; 114k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finish a sync with scattered bullets and no clear record of who committed to what by when.
Who is it for?
Solo founders wearing PM hat who need fast, repeatable minutes after cofounder, contractor, or user interviews.
Skip if: Legal deposition-grade verbatim transcripts, automated calendar scheduling, or real-time transcription pipelines without human themes.
When should I use this skill?
Taking meeting notes, summarizing discussions, tracking action items, or when the user mentions meeting notes, minutes, or structured meeting documentation.
What do I get? / Deliverables
You get a shareable minutes doc with decision checkmarks, an owner/deadline action table, and next steps suitable to send within a day of the meeting.
- Markdown meeting doc with agenda and per-topic discussion
- Decisions list and action-items table with owner and deadline
- Parking lot and next-steps section
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Planning and alignment notes most often anchor sprint and scope conversations during active product build. PM subphase covers rituals, action tracking, and team sync documentation this template standardizes.
Where it fits
Turn a cofounder scope call into decisions and a dated action-item table for the sprint board.
Document user interview themes and follow-up tasks after discovery calls.
Summarize a customer success check-in with explicit owner assignments for bug fixes.
Capture retro outcomes and next-step owners after an outage postmortem.
How it compares
Use instead of freeform chat summaries when you need a fixed PM artifact with an action-item table stakeholders can scan.
Common Questions / FAQ
Who is meeting-notes for?
Solo and indie builders who run lean team syncs, user calls, or advisor check-ins and want consistent documentation from their coding agent.
When should I use meeting-notes?
Use it in Build (pm) for sprint planning; in Grow (support) after customer calls; in Operate (iterate) for retrospective or incident review notes; whenever you mention meeting minutes or action items.
Is meeting-notes safe to install?
It is a formatting and summarization template with no prescribed shell access; review the Security Audits panel on this page before installing any skill from the catalog.
SKILL.md
READMESKILL.md - Meeting Notes
# Meeting Notes You are an expert at creating clear, actionable meeting summaries and notes. ## When to Apply Use this skill when: - Taking meeting notes - Summarizing discussions - Tracking action items and decisions - Creating meeting minutes - Documenting team syncs ## Meeting Notes Structure ```markdown # [Meeting Title] **Date**: [Date] **Time**: [Time] **Attendees**: [Names] **Note Taker**: [Name] ## Agenda - [Topic 1] - [Topic 2] ## Key Discussion Points ### [Topic 1] - [Summary of discussion] - [Key points raised] ### [Topic 2] [Continue for each topic...] ## Decisions Made - ✅ [Decision 1] - ✅ [Decision 2] ## Action Items | Action | Owner | Deadline | Status | |--------|-------|----------|--------| | [Task description] | [Name] | [Date] | [ ] To Do | ## Next Steps - [What happens next] - [Next meeting date if applicable] ## Parking Lot - [Items tabled for later discussion] ``` ## Best Practices - **During Meeting**: Capture key points, not verbatim - **After Meeting**: Send notes within 24 hours - **Action Items**: Specific, assigned, with deadlines - **Decisions**: Clear and documented - **Concise**: Focus on outcomes, not process --- *Created for meeting documentation and action tracking*