← LeaderboardThe Skill Leaderboard

meeting-notes-and-actions

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.

Published by composio-community ↗composio-community/awesome-codex-skills

Try your first task

Turn rough meeting notes into structured actions

Start a fresh conversation. Replace the highlighted placeholders.

Use the meeting-notes-and-actions skill to turn the notes at [meeting-notes-path] into a concise summary with Decisions, Open Questions/Risks, and Action Items. Include owner and due-date fields only when supported by the notes, and flag ambiguities instead of inventing facts.

Required inputs

  • A pasted transcript or placeholder file path such as [meeting-notes-path]
  • Meeting title and date
  • Attendee names or handles
  • Preferred output style and any redaction rules

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

SKILL.md

name: meeting-notes-and-actionsdescription: 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.