Menu

Individual skill

meeting-notes-to-actions

0upvotes

Converts raw meeting notes or transcripts into a four-part record - a 3-5 sentence summary, the decisions actually made, an action table with owner, verb-phrased action, due date, and status, and the open questions - without inventing owners, dates, or tasks. Use when someone pastes notes and asks "pull the action items out of this", "summarize this meeting", "who owns what from this transcript", or "what did we actually decide". Do NOT use for preparing the agenda before a meeting happens - use meeting-agenda instead - or for turning extracted actions into engineering tickets - use jira-ticket-writer instead.

skills/meeting-notes-to-actions/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Meeting Notes to Actions

The expensive failure with meeting notes is not messiness - it is the commitment that silently evaporates because nobody wrote down who owns it. This skill extracts, rather than reformats: decisions and commitments come out of the noise, gaps in ownership are made loudly visible instead of papered over, and nothing is invented that was not in the room.

## Operating procedure

### Step 1: gather inputs

- The raw material: notes, transcript, chat log, or bullet dump. Accept it as-is.
- The meeting date if stated or supplied - relative dates like "Friday" can only be resolved to a calendar date when the meeting date is known; otherwise keep the relative form exactly as written.
- Attendee names if available, used only to disambiguate ("Alex" when two Alexes attended); never to guess owners.

If the notes are too thin to extract from (no verbs, no names), say so and return what is extractable rather than padding.