meeting-notes
by Shubhamsaboomeeting-notes is a lightweight skill for turning raw transcripts or notes into structured meeting minutes with agenda, discussion points, decisions, action items, next steps, and a parking lot.
This skill scores 68/100, which makes it acceptable to list but clearly limited for directory users. It gives agents a clear trigger and a useful structured output format for meeting summaries, so it should reduce prompt guesswork versus starting from scratch. However, it is still a lightweight documentation-only skill with little operational detail beyond the template, so users should install it mainly for consistent note structure rather than a robust end-to-end meeting workflow.
- Strong triggerability: the description and 'When to Apply' section clearly name meetings, minutes, action items, and decisions.
- Provides a reusable meeting-notes schema with agenda, discussion points, decisions, action items, next steps, and parking lot sections.
- Best-practice reminders push agents toward actionable notes rather than verbatim transcription.
- No examples, edge-case guidance, or decision rules for incomplete/transcript-based meetings, so agents may still guess.
- The repo provides only a Markdown template and brief best practices; there are no support files, install steps, or executable workflow assets.
Overview of meeting-notes skill
The meeting-notes skill is a lightweight formatting-and-structure aid for turning a rough meeting transcript, chat log, or human notes into clean meeting minutes. Its real job is not transcription; it helps an agent organize what happened into a usable record with agenda, discussion points, decisions, action items, next steps, and a parking lot.
What meeting-notes is best for
Use meeting-notes when you already have meeting content and need a consistent output fast:
- team sync summaries
- project update notes
- stakeholder meeting minutes
- action-item tracking
- decision documentation after a discussion
It is best for people who want reliable structure more than elaborate analysis.
What makes meeting-notes different from a generic prompt
A normal “summarize this meeting” prompt often misses ownership, deadlines, or explicit decisions. The meeting-notes skill gives the model a fixed meeting-notes template, which makes outputs easier to scan, share, and follow up on. That consistency is the main reason to install it.
What users usually care about before installing
Most users evaluating the meeting-notes skill want to know:
- whether it saves time versus a plain prompt
- whether it can handle messy notes
- whether it captures action items clearly
- whether it is too rigid for their meeting style
The answer is: it is useful if your main problem is structure and follow-through, but it is not a substitute for accurate source material.
What this skill does not do
meeting-notes does not add meeting intelligence from nowhere. If attendees, decisions, owners, or deadlines are missing in the input, the output will still have gaps or guessed placeholders. It also does not include repo-side scripts, rules, or reference files to enforce deeper workflows.
How to Use meeting-notes skill
How to install meeting-notes
Install the meeting-notes skill from the repository with:
npx skills add Shubhamsaboo/awesome-llm-apps --skill meeting-notes
After installation, your agent can apply the skill when your request is clearly about meeting notes, meeting minutes, action items, or discussion summaries.
What to read first in the repository
This skill is unusually simple. Start with:
awesome_agent_skills/meeting-notes/SKILL.md
There are no supporting README.md, metadata.json, rules/, or helper scripts in this skill folder, so most of the value is in understanding the output structure and using it well.
What input meeting-notes needs
The meeting-notes skill works best when you provide at least some of the following:
- meeting title
- date and time
- attendees
- rough agenda
- transcript, bullet notes, or chat log
- explicit decisions
- action items with owners and deadlines if known
If you only paste a vague paragraph, expect a generic summary. If you supply raw but detailed notes, the skill becomes much more useful.
Best input formats for meeting-notes usage
Good source material for meeting-notes usage includes:
- a transcript from Zoom, Meet, or Teams
- bullet notes taken during the meeting
- a Slack thread summarizing the discussion
- a voice-note transcription cleaned enough to identify topics
The skill is especially helpful when the source is messy but information-rich.
Turn a rough request into a strong meeting-notes prompt
Weak request:
Summarize this meeting.
Stronger request:
Use the meeting-notes skill to turn these raw notes into formal meeting minutes. Keep the standard sections for Agenda, Key Discussion Points, Decisions Made, Action Items, Next Steps, and Parking Lot. If an owner or deadline is missing, mark it as
TBDinstead of inventing one. Source notes: [paste notes]
Why this works:
- it explicitly invokes the structure
- it prevents fabricated owners and dates
- it tells the model how to handle missing information
A practical prompt template
Use this pattern for more reliable meeting-notes usage:
Use the
meeting-notesskill.
Meeting title: [title]
Date/time: [date/time]
Attendees: [names]
Goal: convert the following raw notes into concise meeting minutes.
Requirements: capture decisions separately from discussion, create an action-items table, and flag missing owners or deadlines asTBD.
Raw notes/transcript: [paste content]
This gives the model enough context to produce a cleaner first draft.
Suggested workflow from raw notes to final minutes
A practical workflow:
- Paste raw notes or transcript.
- Ask for structured output using the
meeting-notesskill. - Review the
Decisions Madesection first. - Check the
Action Itemstable for ownership and due dates. - Ask for a revision to fill gaps, shorten discussion points, or make actions more specific.
- Send or store the final version within 24 hours.
That sequence matches the skill’s emphasis on outcomes over verbatim capture.
How to handle missing details
The biggest source of bad notes is silent guessing. Tell the model to:
- preserve uncertainty
- use
TBDfor unknown owner or deadline - keep ambiguous items out of
Decisions Made - move unresolved topics into
Parking Lot
This small instruction materially improves trustworthiness.
Where meeting-notes fits in a team workflow
The meeting-notes skill is a good fit when your team already has meetings but lacks consistent documentation. It works well for:
- internal project meetings
- recurring standups with decisions
- cross-functional syncs
- client or stakeholder recap notes
It is less valuable if your team needs full transcript analysis, sentiment detection, or compliance-grade records.
meeting-notes skill FAQ
Is meeting-notes worth installing if I can write a prompt myself?
Usually yes, if you repeatedly need the same meeting-notes format. The skill saves prompt-writing time and improves consistency. If you only do this once in a while, a manual prompt may be enough.
Is meeting-notes good for beginners?
Yes. The meeting-notes guide is simple because the skill is mostly a clear template with best practices. Beginners benefit from the default structure, especially the separation between discussion, decisions, and action items.
When should I not use meeting-notes?
Skip meeting-notes when:
- you need verbatim transcripts
- the source material is too incomplete to identify decisions
- you want deep analysis rather than minutes
- your organization has a strict custom meeting-minutes format that conflicts with this template
Does meeting-notes create action items automatically?
It can extract likely action items from the input, but quality depends on the source. If your notes do not state who owns a task or when it is due, the model should not invent those details. For best results, provide explicit owners and deadlines.
How is meeting-notes different from ordinary summarization?
Ordinary summarization compresses content. meeting-notes for Meeting Notes is about operational documentation: what was discussed, what was decided, who owns what, and what happens next. That distinction matters if the notes will drive work after the meeting.
How to Improve meeting-notes skill
Give better source notes, not just longer ones
The fastest way to improve meeting-notes output is to provide cleaner inputs:
- speaker-attributed bullets if possible
- explicit decision statements
- clear owner names
- due dates in a consistent format
A shorter but clearer note set often beats a noisy transcript dump.
Tell the skill what not to invent
Add a constraint like:
Do not fabricate attendees, decisions, owners, or deadlines. Use
TBDwhen missing.
This reduces the most common failure mode in meeting-notes usage: confident-looking but unsupported details.
Force stronger action items
If action items are vague, revise with:
Rewrite the action items so each one contains a concrete task, one owner, one due date or
TBD, and a status.
This is especially useful when the first draft produces soft tasks like “follow up” or “look into it.”
Separate decisions from open discussion
Another common issue is mixing unresolved debate with final outcomes. Improve the result by saying:
Only include items in
Decisions Madeif the source clearly shows agreement or approval. Move unresolved points toParking LotorNext Steps.
That single instruction makes the meeting-notes skill more trustworthy for real team use.
Ask for a second pass optimized for distribution
After the first draft, run one more refinement:
Shorten discussion bullets, keep all decisions and actions, and make the output ready to send to attendees.
This produces notes that are easier to share without losing accountability.
Adapt the template to your operating style
If your meetings are fast and tactical, shorten Key Discussion Points and emphasize Action Items. If your meetings are strategic, keep fuller discussion bullets and decision rationale. The skill’s value comes from structure, but you should still tune the balance to your team’s needs.