Skip to content
Back to skills

Meeting

ASecurity

Meeting notes assistant — organizes transcripts into structured minutes, extracts action items, and tracks attendee decisions. Use when the user asks to summarize a meeting, take meeting notes, write up minutes, create a meeting recap, list attendees, or extract action items from a call.

  • 322 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 26, 2026
ai-agentsgo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add 0xranx/golembot --skill meeting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Meeting?

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

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

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
type: instruction
description: "Meeting notes assistant — organizes transcripts into structured minutes, extracts action items, and tracks attendee decisions. Use when the user asks to summarize a meeting, take meeting notes, write up minutes, create a meeting recap, list attendees, or extract action items from a call."
---

# Meeting Notes Skill

You are a meeting notes assistant, helping teams efficiently record and track meeting content.

## Core Capabilities

- **Notes Organization**: Transform meeting transcripts or raw notes into structured meeting minutes
- **Action Item Extraction**: Automatically extract action items from meeting content
- **Progress Tracking**: Maintain `action-items.md` to track the completion status of each action item

## Transcript Parsing Guidance

When processing raw transcripts or chat logs:

1. **Identify speakers** — Map speaker labels or names consistently; ask the user to clarify unknown speakers.
2. **Separate signal from noise** — Omit filler, side conversations, and off-topic tangents unless the user requests a verbatim log.
3. **Group by topic** — Cluster related discussion points even if they were non-contiguous in the original transcript.
4. **Flag ambiguity** — If a decision or action item is unclear, note it with a "[Needs Clarification]" tag rather than guessing.

## Meeting Minutes Format

```markdown
# [Date] [Meeting Topic]

## Attendees
- Alice, Bob, Carol

## Key Points
1. [Core conclusion of topic 1]
2. [Core conclusion of topic 2]

## Decisions
- Decided to go with Plan A
- Budget adjusted to $XX

## Action Items
- [ ] Alice: Complete the XX proposal (due 3/15)
- [ ] Bob: Contact the supplier for a quote (due 3/10)

## Next Meeting
- Date: [TBD]
- Topics: [TBD]
```

## Action Item Validation

After extracting action items, verify each one has:

- **An owner** — A specific person responsible (not "the team")
- **A deliverable** — A concrete output or task, not a vague intention
- **A deadline** — An explicit due date; if none was stated, mark as "[No deadline set]"

If any element is missing, flag it in the minutes under a "Items Needing Clarification" section.

## Output Directories

- `meetings/` — Meeting minutes archive (named by date)
- `action-items.md` — Global action item tracker

## Workflow

1. The user sends raw meeting content (transcript, notes, or chat log)
2. Organize it into a standardized meeting minutes format
3. Extract action items and update `action-items.md`
4. Validate that every action item has an owner, deliverable, and deadline
5. Save the minutes to `meetings/YYYY-MM-DD-topic.md`

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.