- Home
- Skills
- Business & Operations
- Evidence Labelled Meeting Notes
Works with the AI Agents you already use
Evidence Labelled Meeting Notes
Turn meeting transcripts into accurate, structured notes that distinguish real decisions, estimates, open questions and actions.
Free
Evidence Labelled Meeting Notes
Example session with this skill installed
Turn these fictional project meeting notes into an evidence-labelled record. Separate confirmed facts, estimates, decisions, non-decisions and actions. Don't invent missing owners or deadlines.
Dan: "Auth testing is signed off."
Sam: "That's not correct. We still have an unresolved edge case."
Dan: "Sorry, I confused it with payments testing."
Sam: "It will probably take another two days, but I can't promise that."
Hester: "Should we launch on the 15th?"
Sam: "I'd rather not commit until testing is complete."
Hester: "We'll keep the 15th as a working target, not an agreed date."
Hester: "Someone needs to update the rollback plan."
Dan: "Yes, that needs doing."
Identify what we need to confirm before treating these notes as the final record.
- Read your context and instructions
- Compiled the evidence labelled meeting
Evidence-Labelled Notes: Project Atlas
Source: Supplied fictional meeting notes
Confirmed facts
- Authentication testing has not been signed off. Sam explicitly corrected Dan's statement, and Dan acknowledged his mistake.
confirmed - Dan had confused authentication testing with payments testing.
confirmed
Confirmed decisions
- The 15th remains a working launch target, not an approved launch date.
confirmed
Estimates
- Authentication testing might take approximately two more days. Sam expressly declined to commit to that timeframe.
estimate
Flagged non-decisions
- Launch approval: No agreement to launch on the 15th was reached. The date remains provisional.
- Rollback plan ownership: Updating the document was discussed, but nobody was assigned responsibility.
Actions
| Action | Owner | Timing |
|---|---|---|
| Complete authentication testing | Sam's role in testing is evidenced, but responsibility for completing the work is not formally assigned in these notes | Approximately two days, estimate only |
| Update rollback plan | Unknown | Unknown |
Open questions
- When will authentication testing be signed off?
- Who is responsible for updating the rollback plan?
- What evidence and approval are required to confirm the launch date?
Summary
Authentication testing remains open. The proposed launch date was explicitly left unconfirmed. The rollback plan requires updating, but no owner or deadline was assigned.
Human review required
Confirm the outstanding testing work, assign responsibility for the rollback-plan update and obtain an explicit launch decision before treating any proposed timing as agreed.
Illustrative output from fictional material, not a recorded production run.
Connects securely to your tools. The creator never sees your data.
About this skill
Meeting notes that distinguish what was said from what was agreed
Turn transcripts and meeting notes into a structured record without losing important uncertainty.
Evidence-Labelled Meeting Notes helps you identify what was actually confirmed, which decisions were made, which ideas remain open and who really owns the next actions.
What you'll get
- Confirmed facts separated from assumptions and estimates
- Genuine decisions clearly recorded
- Proposals and working targets flagged as unresolved
- Actions with owners and deadlines only when established
- Conflicting statements and corrections kept visible
- Open questions and a concise meeting summary
- A review checklist before treating the notes as final
Designed for
Project managers, consultants, operations teams and professionals who need dependable records of planning sessions, project reviews, stakeholder meetings and other important discussions.
How to use it
Provide a transcript or sufficiently detailed meeting notes. The skill reviews the source and creates a structured record that preserves the difference between confirmed information and what still needs checking.
No meeting recording or transcription service is included.
Human review remains essential
The skill does not send follow-ups, assign tasks or update connected systems. A person must verify the record before relying on it.
The underlying method is also publicly available under the MIT licence. This Agensi listing packages the workflow and supporting material for use with compatible AI agents.
Requires a legible source transcript or notes. Does not automate follow-ups, system updates, or message delivery.
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 any payment.
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
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 21 days ago
- Free with an Agensi account
Permissions
Designed for agents that support SKILL.md instructions and bundled reference files. Works with pasted meeting notes or transcripts. Reading uploaded documents depends on the host agent. No transcription, recording or external account connection is included.