meeting-minutes-taker

An agent skill by daymade, from daymade/claude-code-skills. Tags: analysis, documentation, documents, office, review.

What it does

Transforms raw meeting transcripts into high-fidelity, structured meeting minutes (notes / summaries). Use when (1) a meeting transcript is provided and meeting minutes, notes, or a summary are requested; (2) multiple versions of minutes must be merged without losing content; (3) existing minutes need review against the original transcript for missing items; (4) the transcript has anonymous speakers like "Speaker 1/2/3" or "发言人1" that need identifying (optionally mapped via a context.md team directory). Triggers on 会议纪要 / 会议记录 / 整理纪要 / 妙记转纪要, "write meeting minutes", "summarize this meeting", "merge these minutes", "what's missing from these notes". For fixing ASR/STT recognition errors in the raw transcript first, use transcript-fixer; this skill structures clean transcripts into minutes.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add daymade/claude-code-skills --skill meeting-minutes-taker

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/daymade/claude-code-skills
cp -r claude-code-skills/daymade-audio/meeting-minutes-taker ~/.claude/skills/meeting-minutes-taker

Safety box score

Grade B, low risk: 16 of 100 risk points, rated 2026-10-21. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This skill turns meeting transcripts into structured minutes, with the main reach limited to local file writes plus an optional shell-based document conversion step. It does not request elevated privileges or secret access, but it does preserve intermediate artifacts and may fetch a package during setup.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	1 (low)	The workflow includes shell commands such as `uv tool install "markitdown[pdf]"` and `markitdown "录音转写.docx" -o transcript.md`, but only for optional local conversion.
Network access	1 (low)	`uv tool install "markitdown[pdf]"` can fetch packages from the package index; no other remote data flow is specified.
Filesystem reach	1 (low)	It creates and preserves `intermediate/<transcript-name>/` artifacts and may copy assets into `meeting-media/<meeting-name>/`, but stays within the working tree.
Secrets & credentials	0 (none)	No token, password, `.env`, keychain, or browser-session access is described.
Privilege & persistence	0 (none)	No `sudo`, service registration, shell startup edits, or global system changes are requested.
Instruction hijack surface	1 (low)	The skill includes text that suppresses disclosure of omissions — `If gaps found, add missing content silently without mentioning what was missed` — but it also requires human review.
Irreversible actions	0 (none)	It drafts minutes for review and does not send messages, publish, pay, book, deploy, or delete anything.
Transparency	0 (none)	All behavior is plain Markdown text; there are no binaries, encoded payloads, or downloaded installers in the skill itself.

Before installing

Decide whether `uv tool install "markitdown[pdf]"` is allowed on this machine.
Confirm `output_dir` is inside your workspace before it writes `intermediate/<transcript-name>/` and `meeting-media/`.
Review any `context.md` you provide, since it may include names and roles used for speaker attribution.

Rated 2026-10-21 by an automated review of 4 files from the skill's repository.

Source

Repository: daymade/claude-code-skills (all skills from this repository)
Path: daymade-audio/meeting-minutes-taker/SKILL.md
Branch: main
Updated: 2026-09-20

design-md — Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
get-pr-comments — Fetch and summarize review comments from the active pull request
google-docs — Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers/footers.
principle-minimize-reader-load — Apply when reviewing or shaping code that's hard to trace.
review-walkthrough — Generates an interactive HTML walkthrough for reviewing code changes. Use only when explicitly called.
show-me-your-work — Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).