# meeting-notes-and-actions

meeting-notes-and-actions turns a meeting transcript or rough notes into a summary with decisions and tasks that each have an owner. Handles Zoom, Meet and Teams transcripts.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1 install · ★ 17383 repo stars
- Author: composio-community
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/composio-community/awesome-codex-skills/tree/HEAD/meeting-notes-and-actions/SKILL.md
- Updated: 2026-07-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/meeting-notes-and-actions

## What it does

Give the skill a transcript, either pasted or as a file path, or a pile of rough notes, and it writes up a structured document. The sections are `Summary`, `Decisions`, `Open Questions/Risks` and `Action Items`, with the last one as checkboxes carrying an owner and a due date. A header lists the meeting title, date and attendees.

Before it starts, it asks for the title and date, who attended and their handles, whether you want terse bullets or prose, how action items should look, and any redaction rules. Then it cleans the text: noisy timestamps and speaker labels go, filler words get trimmed, direct quotes stay untouched. Vague requests become concrete tasks. When the recording gives no deadline, the skill proposes one itself, so check those dates with the people involved before you send anything.

A final pass checks that names are spelled consistently and that nothing was invented; unclear points come back as questions. If timestamps exist it can add a timeline of key moments, and it can write a 2–3 sentence blurb for Slack or email.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add composio-community/awesome-codex-skills --skill meeting-notes-and-actions -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/meeting-notes-and-actions/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/meeting-notes-and-actions/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add composio-community/awesome-codex-skills --skill meeting-notes-and-actions -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/meeting-notes-and-actions/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add composio-community/awesome-codex-skills --skill meeting-notes-and-actions -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/meeting-notes-and-actions/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install composio-community/awesome-codex-skills meeting-notes-and-actions
```

2. **Manually: put the files in place**
- File: `.github/skills/meeting-notes-and-actions/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add composio-community/awesome-codex-skills --skill meeting-notes-and-actions -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/composio-community/awesome-codex-skills --path meeting-notes-and-actions
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/meeting-notes-and-actions/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add composio-community/awesome-codex-skills --skill meeting-notes-and-actions -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/composio-community/awesome-codex-skills/tree/HEAD/meeting-notes-and-actions/SKILL.md

## When to use it
- Turn a Zoom, Meet or Teams transcript into notes the team can read
- Pull the decisions out of a long call
- Assign owners and due dates to follow-ups
- Surface open questions and risks buried in a meeting chat
- Draft a short Slack or email recap

## Example prompts
- Use meeting-notes-and-actions on this Teams transcript and list the decisions and action items by owner.
- Here are my rough call notes. Write them up with risks and open questions, and give every task a due date.
- Add a 2–3 sentence Slack recap under the notes.

## Similar
- [meeting-minutes](https://affpapa.org/en/nevibecode/skills/meeting-minutes.md) — skill · 9881 installs
- [summarize-meeting](https://affpapa.org/en/nevibecode/skills/summarize-meeting.md) — skill · 3300 installs
- [meeting-notes](https://affpapa.org/en/nevibecode/skills/nexu-io-meeting-notes.md) — skill · 233 installs
- [pmstudio-meeting-notes](https://affpapa.org/en/nevibecode/skills/pmstudio-meeting-notes.md) — skill · ★ 328 repo stars
- [meeting-notes-summarizer](https://affpapa.org/en/nevibecode/skills/meeting-notes-summarizer.md) — skill · 3 installs
- [capture-tasks-from-meeting-notes](https://affpapa.org/en/nevibecode/skills/capture-tasks-from-meeting-notes.md) — skill · 1 install

From the same set: [composio-community/awesome-codex-skills](https://affpapa.org/en/nevibecode/by/composio-community/awesome-codex-skills.md) — 2 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
