Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From slim-rebranding
Writes structured meeting summaries with action items from notes, transcripts, or agendas. Enriches context using project files and automates action items via discovered tools.
npx claudepluginhub nasa-ammos/slim --plugin slim-changelogHow this skill is triggered — by the user, by Claude, or both
Slash command
/slim-rebranding:slim-meeting-summaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Writes structured meeting summaries with action items from meeting notes/transcripts/agendas. Leverages workspace context files to enhance accuracy and automatically fulfills action items using discovered automation tools.
Generates structured meeting agendas by gathering context from previous summaries, external services (GitHub, Slack via TECH.md), and custom templates. Automatically detects missing summaries and guides generation.
Structures meeting notes with templates for decisions, action items, and follow-ups following PM best practices.
Generates structured Markdown meeting notes from discussions, with attendees, agenda, key points, decisions, action items, metrics tables, and follow-ups.
Share bugs, ideas, or general feedback.
Writes structured meeting summaries with action items from meeting notes/transcripts/agendas. Leverages workspace context files to enhance accuracy and automatically fulfills action items using discovered automation tools.
Key Features:
Required Skills:
slim-project-aware-workspace: Creates workspace with AGENTS.md and static filesDynamically Discovered Tools (from TECH.md at runtime):
Verify AGENTS.md and all static files exist. Guide user to run slim-project-aware-workspace if missing.
CRITICAL: Load all static files for comprehensive context:
Use context to:
Example enhancements:
Input: "Bob mentioned the auth bug"
+ TEAM.md: Bob Smith (Senior Developer, Auth Team)
→ Output: "Bob Smith (Senior Developer) mentioned authentication service bug"
Input: "Alice will follow up"
+ TEAM.md: Alice Johnson (Project Manager)
→ Action: Assigned to Alice Johnson (Project Manager)
Prompt for input format (markdown/Word/text/paste). Parse and cross-reference with loaded context.
MEETINGS.md matching logic:
MEETINGS.md format:
## Weekly Team Standup
- **Schedule**: Every Monday, 10:00 AM PST
- **Attendees**: Alice (PM), Bob (Dev), Carol (Design)
- **Type**: Status Update
TECH.md parsing logic:
For each section in TECH.md:
- Extract section header (GitHub, Slack, Email, etc.)
- Look for "MCP Server/API/Script:" line
- Extract tool type and availability
- Map to action categories:
* GitHub/Jira → technical tasks (issues, PRs)
* Slack → coordination (messages)
* Email → communication (drafts)
TECH.md format:
## GitHub
- **Resources:**
- https://github.com/org/repo
- **MCP Server/API/Script:** github-mcp-server (installed)
## Slack
- **Resources:**
- #team-channel
- **MCP Server/API/Script:** /usr/local/bin/slack-send.py
Use meeting-summary-template.md. Fill metadata from MEETINGS.md or user input. Apply context from PROJECT.md, TEAM.md, PRODUCTS.md to correct/enrich. Extract action items, assign owners (single or multiple, comma-separated), assign due dates. Generate with markdown lists for multi-value fields.
Create: dynamic/[YYYY-MM-DD]/meeting-summaries/meeting-summary-[title].md (no date in filename)
Scan action items table. For each item, determine if automatable using TECH.md tools. Build list of automatable items with execution plan.
Enter Plan Mode. Present automation plan:
For approved items: use appropriate tool, execute automation, capture results, update table with links/status. For non-automatable items: provide guidance and drafts.
Display file location, show completed/pending items, update summary with results.
Review and Follow This Template:: Meeting Summary Table
Key points:
Static Files Used:
Application:
Can generate agendas for upcoming meetings:
dynamic/[date]/meeting-summaries/Coordination/Communication: Schedule meetings, send messages, share info, coordinate teams Technical: Create issues, fix bugs, implement features, update docs, deploy changes
Build capability map from TECH.md:
Q: Can I use without MCP servers? A: Yes, generates summaries with guidance for manual action items.
Q: What if meeting not in MEETINGS.md? A: Skill prompts for metadata.
Q: How does it correct errors? A: Loads static files and uses context to fix typos/fill missing info.
Q: Multiple owners? A: Yes, comma-separated in Owners column.