← All posts

The Best Meeting and Notes Skills for Claude Code

2026-10-17

The meeting-notes category is small and honest: four skills, each doing one step of a pipeline that most people do by hand and badly.

"Notes" covers at least three different jobs — capturing what was said, structuring it for a reader, and turning it into something publishable. These four skills map onto those jobs.

Capture

baoyu-youtube-transcript — 9.3 · Writing

Downloads YouTube transcripts and subtitles by URL, along with cover images. The highest-scoring skill in this group, and the one that solves the hardest part of the pipeline: getting clean text out of audio or video without a manual pass.

Structure

summarize-meeting — 8.2 · Writing

Turns a meeting transcript into structured notes with date, participants, decisions, and action items. The core skill of the category — what most people mean when they say "meeting notes".

summarize-interview — 7.9 · Writing

A customer-interview variant with Jobs-to-be-Done framing. Different output from meeting notes: it is structured around what the interviewee wants, not what the team decided.

Publish

release-notes — 8.1 · Writing

Generates user-facing release notes from tickets, PRDs, or changelogs. Included here because the raw material overlaps — the same meeting that produces internal notes often produces the changelog that becomes a release note.

The pattern

These four are less a toolkit than a pipeline: capture → structure → (optionally) publish. Each step has a different consumer. A transcript is for you; structured notes are for the team; release notes are for users. Writing them together, from the same source, is what makes the pipeline worth automating.

The scores are honest about difficulty: capture is the most mechanical and scores highest; summary quality depends on the transcript; and structured interview notes are the hardest to get right, which is why they score lowest.

How to choose

The writing category covers the adjacent editing and translation skills.