meeting-notes-to-action-items
- Repo stars 1
- Author updated Live
- Author repo claude-skills
- Domain
- Productivity
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: meeting-notes-to-action-items
description: Convert raw meeting notes, transcripts, or chat logs into decisions, action items, owners, due d…
category: productivity
runtime: no special runtime
---
# meeting-notes-to-action-items output preview
## PART A: Task fit
- Use case: Convert raw meeting notes, transcripts, or chat logs into decisions, action items, owners, due dates, risks, and follow-up questions. Use after syncs, planning sessions, retros, or stakeholder calls..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Core Workflow / Deliver” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Convert raw meeting notes, transcripts, or chat logs into decisions, action items, owners, due dates, risks, and follow-up questions. Use after syncs, planning sessions, retros, or stakeholder calls.”.
- **02** When the source has headings, the agent prioritizes “Overview / Core Workflow / Deliver” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Overview / Core Workflow / Deliver”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: meeting-notes-to-action-items
description: Convert raw meeting notes, transcripts, or chat logs into decisions, action items, owners, due d…
category: productivity
source: 00PrabalK00/claude-skills
---
# meeting-notes-to-action-items
## When to use
- Convert raw meeting notes, transcripts, or chat logs into decisions, action items, owners, due dates, risks, and follo…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Core Workflow / Deliver” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "meeting-notes-to-action-items" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Core Workflow / Deliver
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Meeting Notes To Action Items
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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review