The meeting-notes skill: a transcript in, action items out

The transcript is not the notes. You finish a call, the tool drops 4,000 words of speaker-labeled text in your lap, and the three things you actually agreed to are buried somewhere in the middle. Nobody reads it back. The follow-up gets missed, and two weeks later two people remember the decision differently.

meeting-notes takes that block of text and gives you the short version: a summary written for someone who wasn't on the call, the decisions the group actually landed on, every task assigned to a named person, the questions nobody answered, and what happens next. It works with transcripts from any tool.

The part that earns its keep is the assignment logic. If someone said they'd handle it, it goes to them. If nobody claimed it but the obvious owner was in the room, it goes to them with a flag. If it's genuinely unclear, it says so instead of guessing confidently. It's one of the 55 free skills in our freeskills repo.

Three lines in your terminal. Clone the repo, make the skills folder if it isn't there, copy this one into it.

Restart Claude Code, or open a new session. Install done. There are no API keys to get and nothing to connect, and it never touches your calendar or your meeting tool.

Type /meeting-notes and paste the transcript underneath it. There's no interview and nothing to answer. It reads the whole thing, pulls out the date, the participants and their roles where they're mentioned, then writes the summary, the decisions, the action items grouped by person, any open questions, and the next steps.

It saves to ~/meeting-notes/ using a dated filename like 2026-03-05_q1-product-review.md, then tells you the path, gives you a one-line version short enough to be an email subject, and says how many action items it found and how many it had to flag as unassigned. Sections with nothing in them get left out rather than sitting there empty.

A good first result is one you can forward without editing. Read the action items first. If an owner looks wrong, say so and ask for that one to change.

The simplest run, and the one you'll use most. Paste and go.

Transcripts often miss the date, the real names, or who does what. Hand those over up front and the assignments come out much sharper.

Notes only pay off when someone else reads them. Ask for the follow-up message once the file is written.

Sixty seconds on what this skill does and why it earns its place.

1. 1Hook: there's a brand new free Claude skill that takes you from a 4,000 word transcript nobody will ever read to a clean set of notes with every action item assigned to a name.
2. 2Mechanism: you paste in the transcript. It pulls the participants and the date, writes a summary for someone who wasn't on the call, separates the decisions from the tasks, and assigns every action item to a named person, flagging the ones it had to guess at. It saves the whole thing as a dated file you can forward.
3. 3Transformation: the things you agreed to actually get done. You leave a call, paste the transcript once, and have a file you can forward and a message you can send the room before anyone forgets.
4. 4Close: the notes are free, one of 55 skills. If you want the rest of the admin off your desk too, Claude Code Club is 9 dollars a month. Link below.

Grab the transcript from your last call, run it through tonight, and send the follow-up to whoever was on it. That one message is the whole return.