Claude-skill-registry-data 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.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry-data

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/meeting-notes-and-actions" ~/.claude/skills/majiayu000-claude-skill-registry-data-meeting-notes-and-actions && rm -rf "$T"

manifest: data/meeting-notes-and-actions/SKILL.md

source content

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

Normalize text: strip timestamps/speaker labels if noisy; lightly clean filler words; keep quoted statements intact.
Extract essentials: agenda topics, key decisions, open questions, risks/blocked items.
Action items: who/what/when. Convert vague asks into concrete tasks; propose due dates if missing.
Produce output:
- Header with meeting title, date, attendees.
- Sections:
```
Summary
```
  ,
```
Decisions
```
  ,
```
Open Questions/Risks
```
  ,
```
Action Items
```
  (checkboxes with owner + due).
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.