meeting notes to action items
- Repo stars 1
- Author repo claude-skills
- Domain
- Productivity
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Meeting Notes To Action Items
## Overview
Turn messy notes into a clear record of what was decided and who owns what next.
## Core Workflow
1. Clean the raw notes enough to separate facts, discussion, and side chatter.
2. Extract decisions, unresolved questions, and explicit or implied action items.
3. Assign owners, dates, and dependencies when they are present; mark them as missing when they are not.
4. Surface risks, blockers, and follow-ups that the team could easily forget.
5. Format the result into a concise meeting summary that is easy to send or paste elsewhere.
## Deliver
- Lead with the short summary and key decisions.
- Present action items as concrete verbs with owners and deadlines when known.
- Keep unresolved questions visible instead of hiding them in prose.
## Guardrails
- Do not invent owners or dates.
- Preserve nuance when a decision is tentative.
- Keep the output usable for both participants and absent stakeholders.
Sections and files
Listed in source order.
sections -> Overview → Core Workflow → Deliver → Guardrails
terms -> Turn messy notes into a clear record of what was decided and who owns what next. · 1. Clean the raw notes enough to separate facts, discussion, and side chatter. · - Lead with the short summary and key decisions. · - Do not invent owners or dates.
files/cmd -> no explicit files or commands
body sha256 -> bf1b45fc8ec2
Overview
Turn messy notes into a clear record of what was decided and who owns what next.
Core Workflow
Clean the raw notes enough to separate facts, discussion, and side chatter. Extract decisions, unresolved questions, and explicit or implied action items. Assign owners, dates, and dependencies when they are present; mark them as missing when they are not. Surface risks, blockers, and follow-ups that the team could easily forget. Format the result into a concise meeting summary that is easy to send or paste elsewhere.
Deliver
Lead with the short summary and key decisions. Present action items as concrete verbs with owners and deadlines when known. Keep unresolved questions visible instead of hiding them in prose.
Guardrails
Do not invent owners or dates. Preserve nuance when a decision is tentative. Keep the output usable for both participants and absent stakeholders.