Skip to content
Back to skills

Meeting Notes

ASecurity

Turn raw notes or a transcript into a clean summary with decisions and action items.

  • 11,117 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added August 31, 2026
ai-agentsgo

Security analysis

A100/100

Scanned August 31, 2026

npx -y skills add holaboss-ai/holaOS --skill meeting-notes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Meeting Notes?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Meeting Notes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/holaboss-ai-meeting-notes/badge)](https://www.skillsdirectory.com/skills/holaboss-ai-meeting-notes)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: meeting-notes
description: Turn raw notes or a transcript into a clean summary with decisions and action items.
---

# Meeting Notes

Turn the mess of a meeting — half-sentences, tangents, crosstalk — into a record someone who wasn't there can act on. The value isn't a transcript; it's the decisions, the owners, and the next steps, pulled out and made unambiguous.

## When to use this skill

Use Meeting Notes on raw notes, a rough transcript, or a recording summary to produce a structured recap: what was decided, who owns what, and what's still open. If the goal is to condense an article or report rather than a discussion, use Summarizer instead.

## What a good recap captures

- **Decisions** — what the group actually agreed, stated plainly. Distinguish a decision from a suggestion that went nowhere.
- **Action items** — each with an owner and, where stated, a due date. An action with no owner is a wish; assign it or flag it as unassigned.
- **Open questions** — things raised but not resolved, so they don't quietly vanish.
- **Context** — just enough of the "why" that a decision doesn't read as arbitrary later.

## Principles

- **Signal over transcript.** Don't replay the conversation — extract what matters and drop the rest.
- **Attribute carefully.** Only assign an owner or a decision if the input actually supports it. If it's ambiguous, mark it "unassigned" or "unconfirmed" rather than guessing.
- **Never invent.** If a date, owner, or decision wasn't stated, say so. Fabricated specifics are worse than an honest gap.
- **Neutral voice.** Record what was said, not your opinion of it.

## How to work

1. Read the full input and separate discussion from outcomes.
2. Pull out decisions, then action items (owner + due date where given), then open questions.
3. Write a two-to-three sentence summary at the top so a skimmer gets the gist.
4. Re-check every owner, date, and decision against the source; flag anything you had to infer.

## Output format

Lead with a short **Summary**, then **Decisions**, **Action items** (as a checklist with owners), and **Open questions**. Omit any section that genuinely has nothing in it rather than padding it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…