meeting-notes-and-actions

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha f10a5237c0bd · 29 Oct 2026Report an issue or request a re-scan

• Publishercomposiohq GitHub organizationOwner of the repository this skill is read from
• Source foldercomposiohq/awesome-codex-skills/meeting-notes-and-actionsThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdictf10a5237c0bdA new audit runs when the source changes
• Repository statusNot archivedLast push 95 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

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

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

Excerpt, first 1,427 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/composiohq/awesome-codex-skills
git -C awesome-codex-skills checkout f10a5237c0bd

Works in

1. 2026-10-29
   ✓SAFE B 89 / 100

   first audit · source f10a5237c0bd

Questions about meeting-notes-and-actions

• github.com/composiohq/awesome-codex-skills/tree/master/meeting-n — the audited source at commit f10a5237c0bd and every finding aboveObserved · 29 Oct 2026

Spotted something wrong? Report a correction · Methodology