meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
pinned to #f47f948updated 2 weeks ago
Ask your AI client: “install skills/meeting-notes-to-tasks”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/meeting-notes-to-tasksmetahub onboarded this repo on the author's behalf.
If you own github.com/DevelopersGlobal/ai-agent-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
64
Last commit
2 weeks ago
Latest release
published
- #ai
- #ai-agents
- #antigravity
- #artificial-intelligence
- #claude
- #claude-code-plugin
- #claude-skills
- #codex
- #cursor
- #skills
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.f47f948· 2 weeks ago
Kind-specific
31Skill: SKILL.md present
found at skills/meeting-notes-to-tasks/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
359 words · 2,365 chars · 10 sections
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrentf47f948warn2 weeks ago
Contents
Overview
Meetings produce decisions and commitments. Without structure, these dissolve into vague memory. This skill transforms raw meeting notes into a concrete, actionable task list.
When to Use
- After any meeting with decisions or commitments
- When processing meeting transcripts or notes
- When preparing follow-up communication
Process
Step 1: Extract Decisions
- Read all notes.
- List every decision made:
Decision: [what was decided] - Distinguish decisions from discussions (decisions = agreed outcomes, not explorations).
Deliver: A numbered list of decisions made.
Step 2: Extract Action Items
- For each commitment made, write:
Action: [specific deliverable] Owner: [person's name] Due: [specific date, not "soon" or "next week"] Context: [1-sentence background] - If an owner is not named: flag it — unowned actions are undone actions.
- If a due date is not named: flag it — undated actions are undone actions.
Deliver: Structured action items with owner and due date for every commitment.
Step 3: Identify Blockers and Dependencies
- What action items are blocked by other action items?
- What external dependencies exist (waiting on third party, requires approval, etc.)?
- What open questions remain unresolved?
Deliver: Blocker list and open questions with owners.
Step 4: Draft Follow-Up Summary
- Compose a concise follow-up message:
- Decisions (bullet list)
- Action items (table: action | owner | due date)
- Open questions (bullet list with owner)
- Next meeting date (if applicable)
Deliver: Ready-to-send follow-up email/Slack message.
Common Rationalizations (and Rebuttals)
| Excuse | Rebuttal |
|---|---|
| "Everyone knows what they need to do" | They don't. Write it down. |
| "The notes are good enough" | Notes describe what was said. Action items describe what will be done. |
| "We'll follow up informally" | Informal follow-up means things fall through the cracks. |
Verification
- Every decision captured
- Every action item has: owner, due date, specific deliverable
- Unowned/undated items flagged
- Blockers and open questions identified
- Follow-up summary drafted and ready to send
References
Reviews
No reviews yet. Be the first.
Related
Planning With Files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Guizang Ppt Skill
AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
orchestration-patterns
>
mh install skills/meeting-notes-to-tasks