home / skills / composiohq / awesome-codex-skills / meeting-notes-and-actions

meeting-notes-and-actions skill

safe

This skill converts meeting transcripts into structured notes with decisions, risks, and owner-tagged actions for share-ready outputs.

npx playbooks add skill composiohq/awesome-codex-skills --skill meeting-notes-and-actions

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.4 KB

---
name: meeting-notes-and-actions
description: Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.
metadata:
  short-description: Meeting transcript to notes and actions
---

# Meeting Notes & Actions

Process transcripts into structured notes and action items.

## Inputs to ask for
- Source: pasted transcript/text or file path; meeting title/date; attendees and their handles.
- Output style: terse bullets vs. narrative, action-item format, due date/owner tags, redaction rules if any.

## Workflow
1) Normalize text: strip timestamps/speaker labels if noisy; lightly clean filler words; keep quoted statements intact.
2) Extract essentials: agenda topics, key decisions, open questions, risks/blocked items.
3) Action items: who/what/when. Convert vague asks into concrete tasks; propose due dates if missing.
4) Produce output:
   - Header with meeting title, date, attendees.
   - Sections: `Summary`, `Decisions`, `Open Questions/Risks`, `Action Items` (checkboxes with owner + due).
5) Quality checks: ensure names are consistent; no hallucinated facts; flag ambiguities as clarifying questions.

## Optional extras
- Include timeline of major moments if timestamps exist.
- Provide short Slack/Email-ready blurb (2–3 sentences) plus the full notes.

Overview

This skill turns meeting transcripts or rough notes into crisp, share-ready summaries with decisions, risks, and owner-tagged action items. It accepts pasted text or files from Zoom/Meet/Teams and produces a clean header plus structured sections for quick distribution. Output can be tailored to terse bullets or narrative style and includes optional Slack/Email-ready blurbs.

How this skill works

The skill normalizes raw text by removing noisy timestamps and redundant speaker labels while preserving quoted statements. It extracts agenda topics, key decisions, open questions, and risks, then converts informal requests into concrete action items with owners and suggested due dates. Final output is organized into a header and sections: Summary, Decisions, Open Questions/Risks, and Action Items (checkboxes with owner + due).

When to use it

After long video calls to create a concise, distributable record.
When you need owner-tagged action items from messy chat logs or transcripts.
To convert raw meeting notes into follow-up tasks with suggested due dates.
Before sending a post-meeting update to stakeholders or Slack channels.
When you want to flag ambiguities or potential risks for clarification.

Best practices

Provide meeting title, date, and attendee list to ensure name consistency.
Specify preferred output style (terse bullets vs. narrative) and redaction rules up front.
Paste full transcript or a clean file path; include timestamps if you want a timeline.
Ask the skill to propose due dates only when owners are known to avoid false assumptions.
Review flagged ambiguities and confirm any suggested dates or owners before sharing.

Example use cases

Turn a 90-minute Zoom transcript into a one-page summary with 6 action items and deadlines.
Process a fast-moving team meeting chat into owner-tagged tasks and a two-sentence Slack blurb.
Convert meeting notes into a stakeholder update listing decisions and open risks.
Extract open questions from a customer call and format them for follow-up with owners.
Produce a timeline of major moments for meetings that include timestamps.

FAQ

What inputs does the skill require?

Provide the transcript (pasted or file), meeting title/date, and attendee names or handles; optional preferences include output style and redaction rules.

Will it invent details or dates?

The skill avoids hallucinations, flags ambiguities, and only proposes due dates when clearly indicated or when asked to suggest them.