meeting-action-extractor
Pull the action items and decisions out of meeting notes or a transcript — each with an owner, a due date, and enough context to become a ticket — plus the open questions. Use when asked to extract action items, turn these notes into tasks, who owns what from this meeting, or pull the to-dos from this transcript. Produces the ticket-ready action list (owner + due + context), the decisions made, the open questions with no owner yet, and a flag for any 'someone should…' that never got assigned.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill meeting-action-extractor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Meeting Action Extractor Half of what's decided in meetings evaporates because no one wrote down who owns it and by when. This reads the notes or transcript and pulls out the *commitments* — separating a real action ("Priya will send the spec by Friday") from a wish ("we should really look at that") — attaches an owner and a due date, and flags the orphan tasks nobody actually took, so they don't quietly die. ## What This Skill Produces - **Ticket-ready actions** — each with owner, due date, and one line of context so it can go straight into a tracker - **Decisions made** — what was actually decided (vs. discussed), for the record - **Open questions** — unresolved items with no owner yet - **Orphan flags** — the "someone should…" tasks that were raised but never assigned, surfaced so you can assign or drop them ## Required Inputs Ask for these if not provided: - **The source** — meeting notes or transcript (paste it) - **The attendees** — names/roles, so owners resolve correctly (a "Priya will…" maps to a real person) - **Default due window** — if dates weren't stated (e.g. "assume next Friday unless said"), or leave as [TBD] - **Where these go** — Jira/Linear/a list — tunes the
- What This Skill Produces
- Required Inputs
- Framework: Commitments, Not Chatter
- Output Format
- Actions — [meeting] · [date]
- Decisions
- Open questions (no owner yet)
- ⚠ Orphans — raised, never assigned
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the meeting-action-extractor skill do?
Pull the action items and decisions out of meeting notes or a transcript — each with an owner, a due date, and enough context to become a ticket — plus the open questions. Use when asked to extract action items, turn these notes into tasks, who owns what from this meeting, or pull the to-dos from this transcript. Produces the ticket-ready action list (owner + due + context), the decisions made, the open questions with no owner yet, and a flag for any 'someone should…' that never got assigned.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill meeting-action-extractor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.