meeting-to-tasks — Claude Code skill: what it does, how to install
meeting-to-tasks parses meeting transcripts into structured action items with assignees and deadlines, catches implicit commitments, and exports tasks for issue trackers.
MIT 255 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill meeting-to-tasks -a claude-codeWhat meeting-to-tasks does
This skill processes raw text, Markdown notes, and transcript files exported from Zoom, Google Meet, Microsoft Teams, Otter.ai, Fireflies, or Rev. It reads the whole transcript before extracting items, figures out the meeting type, and separates final decisions from unresolved questions and discussion points.
Each extracted task starts with an action verb and retains its exact source quote. When participants use vague timing like "soon" or "ASAP", the skill converts that into explicit dates flagged for human review. It also spots contradictory commitments, groups items by owner, creates task files for Linear or GitHub Issues, and always writes a follow-up email draft.
Transcripts below roughly 100 words fail validation, causing the skill to stop and ask for the missing participants or meeting purpose.
What it helps with
- extract actionable tasks and owners from messy call transcripts
- capture implicit commitments participants made during conversation
- export structured task files for Linear or GitHub Issues
- generate post-meeting follow-up email drafts automatically
Example prompts for the agent
- Extract from
transcript.txtand list all action items - Generate tasks for Linear from
meeting-notes.md - Draft follow-up email based on the latest call transcript
How to install meeting-to-tasks
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill meeting-to-tasks -a claude-code2Manually: put the files in place
~/.claude/skills/meeting-to-tasks/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/meeting-to-tasks/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill meeting-to-tasks -a codex2Manually: put the files in place
.agents/skills/meeting-to-tasks/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill meeting-to-tasks -a cursor2Manually: put the files in place
.cursor/skills/meeting-to-tasks/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills meeting-to-tasks2Manually: put the files in place
.github/skills/meeting-to-tasks/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill meeting-to-tasks -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path meeting-to-tasksManually: put the files in place
.devin/skills/meeting-to-tasks/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill meeting-to-tasks -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about meeting-to-tasks
How to install meeting-to-tasks in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill meeting-to-tasks -a claude-code. The skill will be placed in ~/.claude/skills/meeting-to-tasks/SKILL.md.
What transcript sources can meeting-to-tasks process?
It accepts plain text, Markdown notes, or transcripts exported directly from Otter.ai, Fireflies, Rev, Zoom, Google Meet, and Microsoft Teams.
How does meeting-to-tasks handle unclear owners or deadlines?
Ambiguous dates receive a proposed calendar date marked for verification. If an owner is unclear, the skill lists possible candidates or labels the item Unassigned.
Source text
SKILL.md · MIT
---
name: meeting-to-tasks
description: Takes meeting transcripts, extracts action items with owners and deadlines, detects implicit commitments, generates structured meeting summaries, and outputs task files compatible with Linear, GitHub Issues, and other project management tools.
tools: Read, Write, Bash, Grep
model: inherit
---
# Meeting to Tasks
Transform raw meeting transcripts into structured, actionable outputs: decisions, action items, owners, deadlines, and open questions -- including implicit commitments participants may not realize they made.
## Contents
- `references/extraction-schema.md` -- YAML field schemas for every extraction phase
- `references/markers.md` -- Decision/action/implicit markers, priority + deadline inference, confidence scoring
- `references/output-templates.md` -- Meeting summary, task files (Linear/GitHub/generic), follow-up email, directory layout
- `references/meeting-types.md` -- Meeting-type detection and per-type focus
## Workflow
1. **Accept input.** Handle plain text, Markdown, pasted text, audio transcript exports (Otter.ai, Fireflies, Rev, Zoom, Google Meet, Microsoft Teams), or structured notes.
2. **Validate.** Confirm there is enough content (~100 words minimum), identifiable speakers, a discernible topic, and any timestamps. If input is too sparse, ask for the full transcript, the participant list, or the meeting purpose before proceeding.
3. **Read the full transcript first.** Do not extract from a partial read -- later context can change earlier interpretation.
4. **Detect the meeting type** and adjust focus per `references/meeting-types.md`.
5. **Extract in phases** using the schemas in `references/extraction-schema.md`: metadata, decisions, action items, open questions, parking lot, discussion points. Apply the markers and inference rules in `references/markers.md`. Preserve the exact source quote for every item.
6. **Identify speakers.** Build the participant list from speaker labels and track who said what. When labels are absent, infer from context clues, otherwise mark "Unassigned" and flag for the user to assign.
7. **Score confidence** on every item (high/medium/low). Flag all low-confidence items for human review per `references/markers.md`.
8. **Resolve conflicts and ambiguity:** flag contradictory commitments as "CONFLICT" with both versions; list all candidates for unclear ownership; translate vague deadlines ("soon", "ASAP") to specific dates and flag for confirmation; offer both readings of ambiguous scope; consolidate duplicates.
9. **Generate outputs** using `references/output-templates.md`. Confirm which project management format(s) the user wants before generating task files. Always generate the follow-up email, even if unasked.
10. **Post-process:** deduplicate overlapping items; map dependencies; highlight the critical path; report owner imbalance; warn on deadline clustering; list items missing owners or deadlines.
## Rules
- Make action items actionable: start each with a verb, specific enough that the owner knows exactly what to do. Transform "Think about pricing" into "Research competitor pricing and propose new pricing tiers by [date]."
- Err toward capturing too much; a flagged low-confidence item beats a missed commitment.
- Do not editorialize. Report what was said; keep any analysis in clearly labeled "Analysis" sections.
- Respect privacy. If the meeting contains HR issues, personal matters, or confidential information, flag it and ask how to handle it in outputs.
- Handle multi-language transcripts: extract in the primary language and note language-specific nuances.
- Maintain an extraction log noting confidence levels, ambiguities, and decisions made during extraction.
## Quick Commands
- "Extract from [file]" -- Full extraction from the specified transcript
- "Just action items" -- Action items only (skip decisions, questions, summary)
- "Generate tasks for Linear" / "Generate tasks for GitHub" -- Action items in that format
- "Draft follow-up email" -- Follow-up email only
- "Who owes what?" -- Owner-grouped view of all action items
- "What was decided?" -- Decisions only
- "What is still open?" -- Open questions and unresolved items
© OneWave-AI · MIT · OneWave-AI/claude-skills