About meeting-notes
A meeting-documentation skill for creating concise summaries, minutes, decisions, and assigned action items. When the Notion MCP connector is available, it can retrieve earlier meeting context and save notes to a workspace.
Key features
- 01Meeting summaries and minutes
- 02Decision and action-item tracking
- 03Prior meeting context from Notion
- 04Save notes to a Notion workspace
- 05Structured meeting-note template
Use cases
- 01Documenting a team sync
- 02Summarizing a discussion
- 03Carrying unresolved items between meetings
- 04Saving draft and finalized minutes in Notion
MCP support
Optionally uses the Notion MCP connector to retrieve prior notes and attendee details, and create or update meeting pages in Notion.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ infrasity-labs/ dev-gtm-claude-skills --skill meeting-notesAfter installing, type/meeting-notesin Claude Code to confirm it loaded.
Details
From the project READMEMeeting 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
Notion MCP (Optional)
This skill integrates with the Notion MCP connector when available. At the start of the workflow, attempt notion-query-data-sources. If it returns results, Notion is connected — run both Step A and Step B below. If it fails or is unavailable, skip both steps silently, generate notes to chat as normal, and append the alert at the end.
Step A — Before generating notes (prior context pull)
If Notion connected:
- Call
notion-query-meeting-notes— pull the last 2–3 meetings on this same topic or with these attendees - Surface any recurring action items that were never closed and open questions carried over from prior sessions
- Call
notion-get-usersto resolve attendee names to workspace users — pre-populate the Attendees field - Use this prior context to enrich the notes you generate (carry-forward items, open threads, patterns)
If not connected: skip, proceed directly to note generation.
Step B — After generating notes (save to workspace)
If Notion connected:
- Call
notion-searchwith the meeting title to check for an existing Meetings database - If a Meetings database exists: call
notion-create-pagesto save as a new page with properties — Title, Date, Attendees, Status = "Draft" - If no Meetings database found: call
notion-create-databaseto initialize one (properties: Title, Date, Attendees, Status), thennotion-create-pagesto save - After the user confirms the notes are complete, call
notion-update-pageto set Status = "Final" - Confirm to the user: "✅ Meeting notes saved to Notion → [page title]"
If not connected:
💡 Notion not connected — notes output to chat only. Connect the Notion MCP connector to automatically save notes to your workspace and pull prior meeting context before each meeting. Setup: notion-mcp-server
Meeting Notes Structure
# [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