composio-community/awesome-codex-skills

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.

First seen Jan 24, 2026

Installation

$ npx skills add composio-community/awesome-codex-skills --skill meeting-notes-and-actions

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from composio-community/awesome-codex-skills · top by installs.

npx skills add composio-community/awesome-codex-skills

Browse all from composio-community/awesome-codex-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 16.3K
Default branch master
Open issues 13
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
short-description
Meeting transcript to notes and actions

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,430 B
  • docs SUMMARY.md 248 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 569 installs

SKILL.md

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).

  1. 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.