meeting-agenda for Claude Code: a skill for agendas built around decisions

meeting-agenda is a skill that creates one- or two-page meeting agendas with decisions and next actions visible at a glance. This post covers the problem it solves, who it suits, how to install it and run it for the first time, and the one limit you should plan around.

What problem it solves

Many agendas are a list of topics. The meeting covers each one, time runs out, and nobody can say afterward what was decided or who does what next. meeting-agenda changes the shape of the document instead of the meeting. Each decision item must carry at least two options and a decision method, and each next action must name one owner and one deadline. The skill checks these rules after it fills the template, so an agenda with a single option or an action without a date does not pass.

It also picks the format to match the meeting. Regular check-ins get type A, a one-page format centered on tables. Major decisions, such as contracts or changes in direction, get type B, a two-page briefing meant for reading in advance. Meetings with an outside organization get type C, which drops the recommendation column from the decision table and schedules backward from the other party’s launch or opening date.

Who it fits

The chapter rates four situations. Three are enough to decide.

Situation	Fit	Reason
A team lead organizing weekly meeting topics	Good fit	Type A and review of past actions
Preparing a briefing to settle contract terms	Good fit	Type B option comparison and recommendations
Writing minutes after a meeting	Poor fit	Creates agendas only

Preparing a discussion with a publisher or client sits in the middle. It works, but you will adjust the templates to the other organization’s habits.

Install and first run

Copy the skill file and its three templates from the repository root into your Claude Code skill folder.

# From the repository root, copy SKILL.md and templates to the Claude Code skill folder
mkdir -p ~/.claude/skills/meeting-agenda/templates
cp 02-skills/meeting-agenda/SKILL.md ~/.claude/skills/meeting-agenda/
cp 02-skills/meeting-agenda/templates/*.md ~/.claude/skills/meeting-agenda/templates/

Then write your meeting notes after the command. You can append A, B, or C to choose a template yourself.

/meeting-agenda Weekly meeting tomorrow. Review last week's three actions and decide on a new hire.

If you do not name a type, the skill asks about the participants, how heavy the decisions are, and whether the meeting recurs, and then chooses one. It fills the template, checks options, owners, and deadlines, and hands you the agenda as Markdown. The copy commands cover Claude Code paths only, and the repository does not explain how to use the skill in Codex.

What trips people up

Output stops at Markdown. If the agenda has to go out as a Word file or PDF, hand it to a Word skill or to Google Docs as a separate step, and check the page limit after conversion, since one- and two-page limits are the point of the format. The templates also carry example values from the author’s organization, so adjust the meeting formats, the list of decision methods, and the file naming rules to your own team before you rely on them.

Where this comes from

This post adapts part of chapter 01-08 of The Claude Code & Codex Skills Guidebook. The full chapter covers the shared four-block structure behind all three templates and what the missing license file means for sharing modified versions, and the book has 52 more skills like this one. Read the full chapter in The Claude Code & Codex Skills Guidebook on Leanpub.