Meeting Notes And Actions
- 440 installs
- 15.6k repo stars
- Updated July 26, 2026
- composiohq/awesome-codex-skills
meeting-notes-and-actions is a Productivity & Planning skill that turns meeting transcripts or bullet notes into structured summaries, decisions, owner-tagged action items, and risk callouts for engineering standups, pla
About
meeting-notes-and-actions is a Productivity & Planning skill from composiohq/awesome-codex-skills that converts meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items. The skill accepts pasted transcript text or file paths from Zoom, Google Meet, Microsoft Teams, call notes, or long meeting chats, then normalizes timing noise and outputs share-ready notes in terse bullets or narrative form. Developers reach for meeting-notes-and-actions after standups, sprint planning, architecture reviews, or stakeholder syncs when the team needs consistent action-item formatting with due dates, owners, and redaction rules applied.
- Extracts decisions and open questions
- Assigns owners and due dates to actions
- Groups notes by topic or agenda item
- Surfaces blockers and dependencies
- Outputs concise recap formats for Slack or docs
Meeting Notes And Actions by the numbers
- 440 all-time installs (skills.sh)
- Ranked #789 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/composiohq/awesome-codex-skills --skill meeting-notes-and-actionsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 440 |
|---|---|
| repo stars | ★ 15.6k |
| Last updated | July 26, 2026 |
| Repository | composiohq/awesome-codex-skills ↗ |
How do you turn meeting transcripts into action items?
Turn meeting transcripts or bullet notes into structured summaries, decisions, owners, and action items for standups, planning, and stakeholder syncs.
Who is it for?
Engineering leads and developers who need consistent standup, planning, or stakeholder notes from raw Zoom, Meet, or Teams transcripts.
Skip if: Teams that require formal legal meeting minutes, court-ready records, or real-time live transcription inside the meeting tool itself.
When should I use this skill?
A meeting transcript, call notes, or long chat log needs structured summaries, decisions, and owner-tagged action items.
What you get
Structured meeting summaries, decision logs, risk callouts, and owner-tagged action items with due dates ready to share.
- structured meeting summary
- owner-tagged action items
- decision and risk log
Files
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.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What inputs does meeting-notes-and-actions accept?
meeting-notes-and-actions accepts pasted transcript text or file paths from Zoom, Google Meet, Microsoft Teams, call notes, or long meeting chats, plus meeting title, date, attendees, and output style preferences.
What outputs does meeting-notes-and-actions produce?
meeting-notes-and-actions produces structured summaries with decisions, risks, and owner-tagged action items in terse bullets or narrative form, including optional due dates and redaction rules.
When should engineering teams use meeting-notes-and-actions?
Engineering teams should use meeting-notes-and-actions after standups, sprint planning, or stakeholder syncs when a raw transcript must become share-ready notes with clear owners and action items.