meeting-notes
Skill1 starsChanged 8 months agoMITView on GitHub
Turn meeting transcripts or voice recordings into structured notes with action items, decisions, and owners. Use when the user shares a transcript, meeting recording, or asks to summarize a meeting. Triggers on: "meeting notes", "summarize this meeting", "action items from", "what was decided", "meeting summary", "standup notes".
- Installs packages
57 other projects use a version of this.
Adopted by
Most recently taken up by
- Kuan-AI-com/agent-skillstheir own version, first seen Nov 15, 2026
- t128n/skillstheir own version, first seen Nov 8, 2026
- desertcache/agent-ostheir own version, first seen Nov 1, 2026
- juliomrqz/skillstheir own version, first seen Nov 1, 2026
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- Works-HQ/ai-brain-starter-packtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use email-draft, status-report and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
yakatotechSkillemail-draft
Create business email drafts. Use when asked to draft emails
Also in 3 projects that use this
AnthropicSkillstatus-report
Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.
Also in 3 projects that use this
QuixiAISkillweekly-review
Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week
Also in 8 projects that use this
vijpatel7Skillcold-outreach
Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.
Also in 3 projects that use this
LangChainSkillweb-research
Use this skill for requests related to web research; it provides a structured approach to conducting comprehensive web research
Also in 4 projects that use this
jacobraskSkillcalendar
Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.
Also in 3 projects that use this
Other versions57 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 57
- mergisi/awesome-openclaw-agents★ 4.1ksame name
- shiwenwen/hope-agent★ 1.9ksame name
- claude-office-skills/skills★ 433same name
- zrosenfield/sharepoint-ai-skills★ 96same name
- duncan-buildroom/freeskills★ 65same name
- jezweb/vite-flare-starter★ 49same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- charlie947/life-automation-skills★ 25same name
- arezous/pm-pilot★ 20same name
- codeApe-7/ai-agent-workflowGroup★ 18same name
47 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- deploy-kitSkill
- figma-bridgeSkill
- job-hunterSkill
- project-kickstartSkill
- slide-deckSkill
- smart-cost-trackerSkill
- social-posterSkill
- supabaseSkill
- translateSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
When the user provides a meeting transcript (text, file, or audio), extract and organize:
- Distinctive: line 97
When asked "show past meetings" or "meeting history":
- Distinctive: line 110
If the user provides an audio file:
- Very specific: line 111
Check if Whisper CLI is available (which whisper)
- Very specific: line 112
If yes: transcribe with whisper [file] --output_format txt
- Very specific: line 113
If no: tell user to install: pip install openai-whisper or use the OpenAI Whisper API
- Distinctive: line 118
Keep summaries concise — 2-3 sentences per topic, not a full transcript
- Distinctive: line 120
Never add content that wasn't in the meeting — only summarize what's there
- Distinctive: line 121
If speakers aren't identified, use Speaker 1, Speaker 2, etc.
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting Notes
You turn messy meeting transcripts into clean, structured, actionable notes.
Core Behavior
When the user provides a meeting transcript (text, file, or audio), extract and organize:
- Attendees — who was there
- Key decisions — what was decided
- Action items — who does what by when
- Discussion points — what was talked about
- Open questions — unresolved items
Output Format
# Meeting Notes — [Date]
**Topic:** [Meeting topic]
**Attendees:** [Names]
**Duration:** [Time]
## Decisions
- [Decision 1]
- [Decision 2]
## Action Items
| Owner | Task | Due |
|-------|------|-----|
| [Name] | [What they need to do] | [When] |
| [Name] | [What they need to do] | [When] |
## Discussion Summary
### [Topic 1]
[2-3 sentence summary of what was discussed]
### [Topic 2]
[2-3 sentence summary]
## Open Questions
- [Question that wasn't resolved]
- [Item that needs follow-up]
## Raw Quotes (Notable)
> "[Important quote]" — [Speaker]Commands
"Meeting notes from [transcript]"
Parse the transcript and generate structured notes.
"Action items only"
Extract just the action items table — skip everything else.
"What did [person] commit to?"
Filter action items for a specific person.
"Follow up on last meeting"
Load the most recent meeting notes from ~/.openclaw/meetings/ and show overdue action items.
"Standup notes"
Shorter format for daily standups:
# Standup — [Date]
## [Person 1]
- Yesterday: [what they did]
- Today: [what they'll do]
- Blockers: [any blockers]
## [Person 2]
...Meeting Log
Save all meeting notes to ~/.openclaw/meetings/[date]-[topic].md
When asked "show past meetings" or "meeting history":
# Meeting History
| Date | Topic | Action Items | Status |
|------|-------|-------------|--------|
| Mar 27 | Sprint planning | 5 items | 3 done, 2 pending |
| Mar 25 | Design review | 3 items | all done |
| Mar 20 | Dr. Wu check-in | 4 items | 1 overdue |Audio Handling
If the user provides an audio file:
- Check if Whisper CLI is available (
which whisper) - If yes: transcribe with
whisper [file] --output_format txt - If no: tell user to install:
pip install openai-whisperor use the OpenAI Whisper API - Then process the transcript as normal
Rules
- Action items MUST have an owner and a due date. If not mentioned, mark as "TBD"
- Keep summaries concise — 2-3 sentences per topic, not a full transcript
- Preserve exact quotes for important decisions or commitments
- Never add content that wasn't in the meeting — only summarize what's there
- If speakers aren't identified, use Speaker 1, Speaker 2, etc.
- Save all notes to ~/.openclaw/meetings/ for future reference
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

