Meeting To Actions
Help PMs turn raw meeting notes into structured, prioritized action items. Use after any meeting to extract decisions and next steps.
Install
$ agentstack add skill-hardiktiwari-pm-operating-os-meeting-to-actions ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hardiktiwari-pm-operating-os-meeting-to-actions) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Meeting to Actions
Help PMs process meeting notes and extract structured, prioritized action items. Turns unstructured discussion into clear ownership and deadlines.
When to Use
- Processing meeting notes
- Extracting action items from a discussion
- Creating follow-up tasks from a workshop or brainstorm
- When asked "what did we decide?" or "what are the action items?"
- Post-meeting recap and distribution
Process / Template
1. Review Raw Notes
- Identify decisions made
- Identify open questions
- Identify commitments and next steps
- Note any blockers or dependencies
2. Extract Action Items
For each action, capture:
- Action — what needs to be done (verb-first, specific)
- Owner — who is responsible
- Due date — when it's due
- Dependencies — what must happen first
- Type — decision, deliverable, follow-up, blocker
3. Prioritize
- P0 — Must do before next meeting or milestone
- P1 — Important, should do soon
- P2 — Nice to have, can defer
4. Structure the Output
Decisions Made
- Bullet list of decisions with brief context
Action Items | Priority | Action | Owner | Due | Dependencies | |----------|--------|-------|-----|--------------| | P0 | [Action] | [Name] | [Date] | [If any] |
Open Questions
- Questions that need resolution (with owner if known)
Blockers / Risks
- Anything that could derail progress
5. Validate
- Every action has an owner
- Due dates are realistic
- No duplicate or overlapping actions
- Decisions are clearly stated
Output
A Meeting-to-Actions document with:
- Decisions made (for record)
- Prioritized action items with owners and dates
- Open questions
- Blockers/risks
Format: scannable, copy-paste ready for Slack, email, or project tool.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hardiktiwari
- Source: hardiktiwari/PM-operating-OS
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.