Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add genspark-ai/genoffice --skill meeting-minutes -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/meeting-minutes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/meeting-minutes/

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.

meeting-minutes official github Turns a transcript or rough notes into short internal meeting minutes: decisions, action items with owner and due date, open questions. CX Codex +1 9,881installs meeting-minutes-generator datadrivenconstruction The meeting-minutes-generator skill generates structured meeting minutes for construction projects, tracking decisions and action items. Requires Python 3. CX Codex +1 126installs meeting-notes gasserane meeting-notes — a skill for Claude Code that turns raw meeting records into structured action sheets. Handles audio files, handwritten scans, Teams transcripts, and docx comments. CX Codex +1 313installs meeting-minutes-taker daymade The meeting-minutes-taker Claude Code skill turns meeting transcripts into structured minutes with decisions and action items. It merges drafts and checks existing minutes against the transcript. CX Codex +1 1,600installs minutes_merge_input nwverse The minutes_merge_input Claude Code prompt formats meeting data as structured minutes. It separates the meeting into parts and groups notes into points, decisions, tasks, and open questions. GP ChatGPT ★ 395repo stars docx SeifBenayed Skill for creating, reading, and modifying Word documents (.docx) via the Document tool and direct XML editing. CX Codex +1 ★ 116repo stars Safe Docx UseJunior Safe Docx is an MCP server for Claude Code that makes targeted edits to .docx and .odt files while preserving layout. It can revise contract wording and save versions with revision history. CX Codex +1 ★ 48repo stars

From the same set65

The whole set →
qc-visual qc-visual inspects slide layouts to fix overlaps, bad contrast, and alignment issues from screenshots. Keeps original copy, palettes, and fonts intact. GP ChatGPT ★ 12,746repo stars shape-image The shape-image prompt guides Claude Code in adding shapes, labels, and in-cell trend charts to spreadsheets. Use it to annotate key figures or show a data pattern without adding chart objects. GP ChatGPT ★ 12,746repo stars _format Defines the authoring format for ops/*.md files that document canonical edit operations in the genoffice slide editor. GP ChatGPT ★ 12,746repo stars data-attribution The data-attribution prompt for Claude Code defines how to cite external sources in spreadsheets, using a Source column, a footer block, or a separate Sources sheet. GP ChatGPT ★ 12,746repo stars okr-planner okr-planner splits a team's goals into measurable objectives and key results, then hands back an Excel workbook with an alignment sheet and a review log. CX Codex +1 ★ 12,746repo stars brand-copy brand-copy turns product details and target audience inputs into Markdown taglines, selling points, and brand stories. CX Codex +1 ★ 12,746repo stars job-description job-description is a Claude Code skill that turns a hiring request into a job description and resume screening criteria. It asks for missing role details, then prepares a Word document. CX Codex +1 ★ 12,746repo stars campaign-planner campaign-planner turns campaign goals and a budget into a review-ready Word document with run-of-show, materials, budget, KPIs and a retrospective template. CX Codex +1 ★ 12,746repo stars

Project sponsors

Companies that keep this analytics open