meeting-notes

The meeting-notes skill takes raw meeting content and turns it into a summary you can act on. It pulls out what was discussed, what was decided and who agreed to do what, by when.

When Claude Uses It

Claude loads the skill when you give it meeting content or ask it to summarise a meeting. You can also type /meeting-notes to start it directly.

What to Give It

• The path to a transcript file.
• Notes or bullet points pasted into the conversation.
• Some context, such as the project, who attended and what the meeting was for.

Note

The skill reads and writes text only. It has no transcription tool of its own. Transcribe an audio or video recording first, then give Claude the transcript.

What It Does

1. Claude identifies the main discussion topics.
2. Claude extracts the decisions made.
3. Claude lists the action items, each with an owner and a deadline where the content gives one.
4. Claude notes any follow-up meetings or deadlines mentioned.
5. Claude writes the summary and saves it to the project folder.
6. Claude offers to create follow-up tasks and suggests sharing the notes with the attendees.

Claude suggests sharing but does not send anything. Sending notes to anyone outside your organisation is a Level 4 action under the Autonomy Levels rule, so Claude asks first.

The Summary Format

# Meeting Notes: Spring Workshop Planning

**Date:** 2026-10-14
**Attendees:** [Names]
**Purpose:** Agree the workshop agenda and venue

## Summary

[Two or three sentences on the outcomes]

## Discussion Points

### Agenda
- Key point

### Venue
- Key point

## Decisions

1. [Decision with context]

## Action Items

| Action | Owner | Due Date |
|--------|-------|----------|
| [Task] | [Name] | [Date] |

## Next Steps

- [Follow-up item]

Under the File Conventions rule, a working file name starts with the date, so notes from this meeting would be saved as 2026-10-14-Spring-Workshop-Planning-Meeting.md in the project folder for P012 “Spring Workshop”.

Where It Takes Its Context

The skill reads .claude/company/team.md and .claude/company/industry.md to recognise attendees and your organisation’s terms. It follows the Content Defaults rule for language and formality. See Company Context Files.

Customising the Skill

The skill file is .claude/skills/meeting-notes/SKILL.md. It is a customisable engine file, so your edits survive /update through a three-way merge.

You can also create a references/ folder inside .claude/skills/meeting-notes/ and add templates for recurring meeting types, default attendee lists for each team or project, standard agendas, and the way you like action items tracked.