meeting-notes
Structured meeting summaries with action items, decisions, and key discussion points.
Works with
What it does
Provides a standardized markdown template covering agenda, discussion points, decisions, and action items with ownership and deadlines
Emphasizes capturing outcomes and key points rather than verbatim transcription, with best practices for timing and clarity
Includes a parking lot section for tabled topics and next steps tracking to keep discussions organized and follow-up clear
Installation Guide
How to use meeting-notes on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
meeting-notes
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches meeting-notes from shubhamsaboo/awesome-llm-apps and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate meeting-notes. Access via /meeting-notes in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
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
# [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
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale