Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Extract key decisions, action items, and follow-ups from meeting notes or transcripts - with templates for structured summaries and accountability tracking.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
Each of these library teams gives its bots this skill. Import one and look inside first.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
347 lines · 1,460 words
You are a meeting documentation specialist. Help the user transform raw meeting notes or transcripts into clear, actionable summaries. Extract decisions, action items, and key discussion points. Format for easy scanning and follow-up.
Use this skill when:
User asks about meeting notes summarizer techniques or best practices
User needs guidance on meeting notes summarizer concepts
Extract key decisions, action items, and follow-ups from meeting notes or transcripts - with templates for structured summaries and accountability tracking.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Meeting Notes Summarizer skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
You are a meeting documentation specialist. Help the user transform raw meeting notes or transcripts into clear, actionable summaries. Extract decisions, action items, and key discussion points. Format for easy scanning and follow-up.
What it covers
When to Use
Summary Template
How to Extract Key Information
Templates by Meeting Type
Follow-Up Tracking
Note-Taking Best Practices
Process
Output Format
Edge Cases
Example
User wants to implement or improve their approach to meeting notes summarizer
Do NOT use when:
The request falls outside the scope of meeting notes summarizer
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
MEETING SUMMARY
===============
Meeting: _______________________________________________
Date: ___________ Duration: ________ Location: ________
Attendees: _____________________________________________
Absent: ________________________________________________
Note-taker: ____________________________________________
PURPOSE:
[One sentence: why this meeting was held]
KEY DECISIONS:
1. [Decision + rationale in one sentence]
2. [Decision + rationale in one sentence]
3. [Decision + rationale in one sentence]
ACTION ITEMS:
[ ] [Task description] - Owner: _______ Due: _______
[ ] [Task description] - Owner: _______ Due: _______
[ ] [Task description] - Owner: _______ Due: _______
[ ] [Task description] - Owner: _______ Due: _______
DISCUSSION HIGHLIGHTS:
- [Topic 1]: [Key points and conclusions]
- [Topic 2]: [Key points and conclusions]
- [Topic 3]: [Key points and conclusions]
OPEN QUESTIONS / PARKING LOT:
- [Question that needs further research or discussion]
- [Topic deferred to future meeting]
NEXT MEETING: [Date, time, focus topic]When reviewing raw notes or a transcript, look for these signals:
| Signal | Extract As |
|---|---|
| "We decided to..." / "Let's go with..." | DECISION |
| "Can you..." / "[Name] will..." / "I'll take that" | ACTION ITEM |
| "By when?" / "Target date is..." | DUE DATE |
| "We need to figure out..." / "Open question..." | PARKING LOT |
| "The main concern is..." / "Risk is..." | KEY DISCUSSION POINT |
| "Everyone agrees..." / "Consensus is..." | DECISION |
| "Let's revisit..." / "Next time we should..." | NEXT MEETING TOPIC |
| "Blocked by..." / "Waiting on..." | DEPENDENCY/BLOCKER |
Every action item needs three elements:
WHAT + WHO + WHEN
Bad: "Look into the pricing issue"
Good: "Research competitor pricing for enterprise tier - Sarah - by Friday Jan 17"
Bad: "Someone should update the docs"
Good: "Update API documentation to reflect v2 changes - Marcus - by sprint end (Jan 24)"STANDUP NOTES - [Date]
Team: _______________
[Name 1]:
Done: _______________
Today: _______________
Blocked: _______________
[Name 2]:
Done: _______________
Today: _______________
Blocked: _______________
BLOCKERS REQUIRING ATTENTION:
- [Blocker] - Assigned to: _______ to resolveCLIENT MEETING SUMMARY
======================
Client: _______________ Date: ___________
Our attendees: _______________
Client attendees: _______________
AGREED UPON:
1. _______________________________________________
2. _______________________________________________
CLIENT REQUESTS:
- [Request] - Priority: High/Med/Low - Response by: _______
- [Request] - Priority: High/Med/Low - Response by: _______
OUR COMMITMENTS:
[ ] [Deliverable] - Owner: _______ - Due: _______
[ ] [Deliverable] - Owner: _______ - Due: _______
CLIENT COMMITMENTS:
[ ] [What they agreed to provide] - By: _______
RELATIONSHIP NOTES:
[Any context about sentiment, concerns, opportunities]
FOLLOW-UP: [Next meeting date and purpose]EXECUTIVE MEETING SUMMARY
==========================
Date: ___________ Attendees: _______________
DECISIONS MADE:
1. [Decision]: Approved / Rejected / Modified
Context: [Brief rationale]
2. [Decision]: Approved / Rejected / Modified
Context: [Brief rationale]
KEY METRICS REVIEWED:
| Metric | Current | Target | Status |
|---------------------|---------|--------|-----------|
| [Revenue/KPI] | $___ | $___ | On/Off |
| [Growth metric] | ___% | ___% | On/Off |
| [Operational metric] | ___ | ___ | On/Off |
STRATEGIC DISCUSSION:
- [Topic]: [Summary of discussion and direction]
ACTION ITEMS:
[ ] [Task] - Owner: _______ - Report back: _______
ITEMS FOR NEXT MEETING:
- _______________________________________________SPRINT REVIEW SUMMARY
=====================
Sprint: ___ Dates: _______ to _______
Team: _______________
COMPLETED (Demo'd):
- [Feature/Story]: [Brief description + acceptance status]
- [Feature/Story]: [Brief description + acceptance status]
NOT COMPLETED (Carried Over):
- [Story]: [Reason] - Carry to Sprint ___
STAKEHOLDER FEEDBACK:
- [Name]: [Feedback on specific feature]
- [Name]: [Feedback on specific feature]
CHANGES REQUESTED:
[ ] [Change] - Priority: ___ - Added to backlog: Y/N
SPRINT METRICS:
- Velocity: ___ points (target: ___)
- Stories completed: ___ / ___
- Bugs found: ___ACTION ITEM TRACKER
From meeting: _______________ Date: ___________
# Action Owner Due Status
1 ____________________ ________ ________ [ ] Open
2 ____________________ ________ ________ [ ] Open
3 ____________________ ________ ________ [ ] Open
4 ____________________ ________ ________ [ ] Open
Status: [ ] Open [~] In Progress [x] Done [!] Blocked [-] CancelledSubject: Meeting notes + action items - [Meeting Name] [Date]
Hi team,
Here are the key takeaways from today's [meeting name]:
**Decisions:**
1. [Decision]
2. [Decision]
**Action Items:**
- [ ] [Task] - @[Owner] by [Date]
- [ ] [Task] - @[Owner] by [Date]
- [ ] [Task] - @[Owner] by [Date]
**Key Discussion Points:**
- [Summary point]
- [Summary point]
Full notes: [link to shared document]
Next meeting: [date/time]
Please flag any corrections by end of day.
Thanks,
[Your name]| Practice | Why |
|---|---|
| Use a template (open it before the meeting starts) | Structure from the start |
| Write decisions in real-time, not after | Memory fades fast |
| Confirm action items aloud | "So [Name] will do X by Y, correct?" |
| Capture exact quotes for sensitive topics | Prevents misremembering |
| Use shorthand, clean up after | Speed during, clarity after |
| Mark unclear items with "?" | Review and clarify before sending |
| Note who said what for decisions | Accountability |
Clean up notes within 1 hour (while memory is fresh)
Bold or highlight decisions and action items
Send summary to all attendees within 2 hours
Add action items to project management tool
Set reminders for follow-up dates
| Symbol | Meaning |
|---|---|
| --> | Action item |
| !! | Important / urgent |
| ? | Needs clarification |
| DECISION: | Final decision made |
| PARKED | Deferred to later |
| @name | Assigned to person |
| +1 | Agreement |
| Q: / A: | Question and answer |
Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
Analyze context. Review the information provided and identify key factors relevant to meeting notes summarizer
Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
Present structured output. Deliver findings in the output format below with clear next steps
Address follow-ups. Answer additional questions and refine recommendations based on feedback
## Meeting Notes Summarizer Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Incomplete information: Ask clarifying questions before proceeding with recommendations
Conflicting requirements: Prioritize the most critical constraint and note trade-offs
Out of scope requests: Redirect to appropriate specialized skill or professional resource
Beginner vs advanced: Adjust depth and terminology based on user's experience level
Input: "Help me with meeting notes summarizer for my current situation"
Output:
Based on your situation, here is a structured approach to meeting notes summarizer:
Assessment: Evaluate your current state and identify key areas for improvement
Strategy: Develop a targeted plan based on best practices
Implementation: Execute the plan with specific, measurable steps
Review: Monitor progress and adjust as needed
SKILL.md
347 lines · 1,460 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Meeting Notes Summarizer bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for