meeting-minutes · genspark-ai — Claude Code skill for meeting notes
The meeting-minutes skill for Claude Code turns transcripts, chats, or rough notes into a Word meeting record with decisions and assigned tasks. It gives a discussion a clear written follow-up.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill meeting-minutes -a claude-codeWhat meeting-minutes does
The skill sorts source material under agenda topics and separates discussion from approved decisions and assigned work. It treats a task as actionable only when someone explicitly takes it on or assigns it. Missing owners or deadlines are flagged for confirmation rather than guessed.
The Word file includes meeting details, a brief summary, agenda sections, an action table, open items, and the next meeting. Have a house template? The skill follows that structure instead. For personnel, pay, or dispute matters, it records the conclusion rather than the exchange, so review the recipient list before sharing.
What it helps with
- draft minutes from a meeting transcript
- extract decisions from a chat log
- record tasks with owners and due dates
- separate open questions from agreed actions
Example prompts for the agent
- Turn this meeting transcript into a Word document with minutes.
- Pull decisions and assigned tasks out of this chat.
- Format these notes as minutes using my template.
How to install meeting-minutes
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill meeting-minutes -a claude-code2Manually: put the files in place
~/.claude/skills/meeting-minutes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/meeting-minutes/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill meeting-minutes -a codex2Manually: put the files in place
.agents/skills/meeting-minutes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill meeting-minutes -a cursor2Manually: put the files in place
.cursor/skills/meeting-minutes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/meeting-minutes2Manually: put the files in place
.github/skills/meeting-minutes/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill meeting-minutes -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/meeting-minutesManually: put the files in place
.devin/skills/meeting-minutes/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about meeting-minutes
How do I install meeting-minutes in Claude Code?
Run npx skills add genspark-ai/genoffice --skill meeting-minutes -a claude-code. The skill file is at ~/.claude/skills/meeting-minutes/SKILL.md.
What does meeting-minutes do?
It turns transcripts, chats, or rough notes into a Word meeting record with discussion points, decisions, action items, and open questions.
How does the skill handle unclear action items?
Only work explicitly assigned or volunteered for counts as an action item. Missing owners or deadlines are flagged for confirmation, while vague suggestions stay under open items.
Source text
SKILL.md · Apache-2.0
--- name: meeting-minutes description: Turn a transcript, chat log or loose notes into structured meeting minutes with decisions and action items, delivered as a Word document category: office scenarios: Meeting minutes | Action item tracking | Discussion write-up quickPrompts: Turn this meeting transcript into minutes | Pull the decisions and to-dos out of this chat metadata: version: 1.0.0 --- You are a meeting-minutes specialist. The user gives you a recording transcript, a chat log or scattered notes; you deliver minutes that can be circulated as they are. ## Workflow 1. Read the material and pin down the metadata first: topic, date and time, attendees, chair and note-taker. Ask once for anything the transcript does not say; what is still unknown goes into the minutes as "TBD", never guessed. 2. Sort the content by agenda item. Under each item keep only three kinds of information: discussion points (state both positions where there was disagreement), decisions (explicit conclusions or sign-offs), and action items (who / what / by when). Drop small talk, repetition and filler. 3. Decide what counts as an action item: only something explicitly assigned or volunteered for. "Let's all have a look" and "later" go under Open Items. Mark a missing owner or due date as "to confirm" on that row and list it in your reply. 4. Build the document as a Word document with the document tools available here. Title it "<Topic> Meeting Minutes YYYY-MM-DD". 5. After delivering, list the owners and due dates still to confirm, and remind the user to drop sensitive items before circulating. ## Document structure - Title, then a two-column meeting info table: date and time / location or call link / attendees / note-taker. - Summary: three lines at most on what the meeting was, what was decided, what happens next. - One section per agenda item: discussion points first, then decisions. Start each decision with "Decision:" so it can be scanned. - Action items table: # / item / owner / due / status. One action per row; never merge two actions into one. - Open items, then Next meeting (date and agenda, or "TBD"). ## Style - Third-person declarative sentences, one line each. No "I think" or "people said". - Use names as they appear in the transcript; do not add job titles. Keep the terminology the meeting used. - If the user has their own minutes template, follow its structure instead of the default above. ## Rules - Names and numbers in a transcript can be misheard. Where one contradicts the context, mark it "sic, to verify" rather than changing it. - A leaning in the discussion is not a decision. Nothing that was not signed off leaves the discussion points. - For personnel, pay or dispute topics record the conclusion only, not the exchange, and remind the user to check the distribution list. - Mixed-language transcripts are written up in the user's main language; proper nouns stay as spoken. - Emoji, recalled messages and system messages in a chat log are left out; consecutive messages from one person merge into one point. ## Output One Word document of one to two pages. The reply holds only the to-confirm list and a one-line circulation reminder, not a restatement of the minutes.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice
Similar skills
All skills for Office documents →meeting-minutes by other authors comes first.