- Home
- Skills
- Productivity
- Meeting Decision Log Skill
Works with the AI Agents you already use
Meeting Decision Log Skill
Transform messy transcripts into structured decision logs with clear owners, deadlines, and action items.
$4.99
Meeting Decision Log Skill
Example session with this skill installed
Here are my notes from the Q4 API migration sync on 2023-11-15. Participants: Sarah, Mike, Alex. We agreed to move to v2 by Dec 1st. Mike will update the docs. Sarah mentioned needing a security review.
- Read your context and instructions
- Compiled the meeting decision log
I have processed the meeting notes from the Q4 API migration sync. I have separated the confirmed decision regarding the v2 migration from the pending tasks and the security dependency.
Meeting Snapshot
- Meeting: Q4 API migration sync
- Date: 2023-11-15
- Participants: Sarah, Mike, Alex
- Purpose: Coordinate migration to v2 API
Decisions Log
| ID | Decision | Rationale | Approver/Owner | Status | Source |
|---|---|---|---|---|---|
| D-001 | Migrate to v2 API by Dec 1st | Not specified | Unassigned | Confirmed | Notes |
Action Items
| ID | Action | Owner | Due date | Dependency | Status |
|---|---|---|---|---|---|
| A-001 | Update API documentation | Mike | Not specified | None | Not specified |
| A-002 | Conduct security review | Sarah | Not specified | None | Not specified |
Open Questions and Risks
| Item | Why it matters | Owner | Due date | Next step |
|---|---|---|---|---|
| Security review scope | Necessary for v2 deployment | Sarah | Not specified | Define review parameters |
Follow-Up Message
Hi team, following our Q4 API migration sync on 2023-11-15, we have confirmed the move to v2 by December 1st. Mike is handling the documentation updates, and Sarah is leading the security review. We still need to define the specific scope for the security review to ensure we hit the Dec 1st deadline.
Next steps
- Mike to provide an ETA for the documentation draft.
- Sarah to confirm the target date for the security review completion.
- Assign a formal owner to track the overall Dec 1st migration deadline.
Connects securely to your tools. The creator never sees your data.
About this skill
Raw meeting notes and transcripts often bury actual commitments under piles of conversational fluff. This skill stops the hunt for "who said they'd do what" by transforming messy documentation into a structured, audit-ready decision log. It strictly separates agreed-upon outcomes from suggested proposals, ensuring team accountability without you having to manually parse hour-long transcripts.
What it does
- Decision tracking extracts explicit agreements, their rationale, and the designated approvers into a structured log.
- Action item extraction identifies concrete, verb-led tasks and assigns accountable owners and deadlines.
- Ambiguity flagging highlights unassigned tasks, missing deadlines, and open questions that need resolution.
- Risk identification captures blockers, dependencies, and unresolved issues that could halt project progress.
- Recap generation drafts concise follow-up messages and next-meeting agendas based on unresolved items.
How it works
- Source ingestion where the user provides raw meeting notes, a transcript, or a bulleted list of discussion points.
- Classification of every statement into categories like Decision, Action Item, Proposal, or Open Question.
- Structured extraction where the agent populates a Decision Log and Action Item table with IDs and ownership.
- Follow-up planning to organize tasks by urgency and draft a summary for the team.
Frameworks & tools
This skill works with raw text, Markdown notes, or transcripts from tools like Zoom, Otter, or Teams. It outputs GitHub-flavored Markdown tables.
Why this beats prompting it yourself
Generic summaries often mistake proposals for final decisions or hallucinate owners when none were named. This skill uses a strict classification logic that preserves uncertainty and flags gaps, preventing the dangerous assumption of consensus where none exists.
Use cases
- Project standups to track shifting deadlines and new blockers across a dev team.
- Stakeholder reviews to log formal approvals and architectural decisions.
- Discovery calls to capture client requirements and follow-up tasks for the sales team.
- Internal syncs to convert rambling discussions into a clear checklist of "who does what next."
Known limitations
Does not support audio files directly. Requires text input. Cannot automatically send emails or update Jira tickets; it provides the text for you to copy.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Productivity.
Requires text transcripts or notes; cannot process raw audio. Does not integrate directly with task managers. Cannot resolve relative dates without a known meeting date.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 18 days ago