meeting-notes

meeting-notes is a skill for Claude Code, Codex from vanthienha199/openclaw-skills. It costs 74 tokens per session (837 once invoked), scanned A, original, MIT.

A tool that turns a meeting transcript or recording into organised notes. It separates attendees, decisions, discussion topics, unanswered questions, and tasks with owners and deadlines.

In plain words
What is it for?
Use it to summarise meetings, list only action items, identify what a person committed to, or record decisions and open questions.
Why use it?
It removes the need to reread a long transcript or rely on memory to find what was agreed. The result makes follow-up work easier to track.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to summarise meetings, list only action items, identify what a person committed to, or record decisions and open questions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vanthienha199/openclaw-skills/meeting-notes
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add vanthienha199/openclaw-skills --skill meeting-notes
Clone the repo
git clone --depth 1 https://github.com/vanthienha199/openclaw-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for meeting-notes

README.md
[![agentmods](https://agentmods.dev/badge/skills/vanthienha199/openclaw-skills/meeting-notes/github.svg)](https://agentmods.dev/skills/vanthienha199/openclaw-skills/meeting-notes)
Your own site
<a href="https://agentmods.dev/skills/vanthienha199/openclaw-skills/meeting-notes"><img src="https://agentmods.dev/badge/skills/vanthienha199/openclaw-skills/meeting-notes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for meeting-notes

Your own site · 80×15
<a href="https://agentmods.dev/skills/vanthienha199/openclaw-skills/meeting-notes"><img src="https://agentmods.dev/badge/skills/vanthienha199/openclaw-skills/meeting-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 837 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.00837
Opus 5 $0.00037 $0.00418
Sonnet 5 $0.00015 $0.00167
Haiku 4.5 $0.00007 $0.00084

Measured 12d ago against content hash 8d3a7c99902f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

meeting-notes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

meeting-notes/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Meeting Notes

You turn messy meeting transcripts into clean, structured, actionable notes.

Core Behavior

When the user provides a meeting transcript (text, file, or audio), extract and organize:

  1. Attendees — who was there
  2. Key decisions — what was decided
  3. Action items — who does what by when
  4. Discussion points — what was talked about
  5. Open questions — unresolved items

Output Format

# Meeting Notes — [Date]
**Topic:** [Meeting topic]
**Attendees:** [Names]
**Duration:** [Time]

## Decisions
- [Decision 1]
- [Decision 2]

## Action Items
| Owner | Task | Due |
|-------|------|-----|
| [Name] | [What they need to do] | [When] |
| [Name] | [What they need to do] | [When] |

## Discussion Summary
### [Topic 1]
[2-3 sentence summary of what was discussed]

### [Topic 2]
[2-3 sentence summary]

## Open Questions
- [Question that wasn't resolved]
- [Item that needs follow-up]

## Raw Quotes (Notable)
> "[Important quote]" — [Speaker]

Commands

"Meeting notes from [transcript]"

Parse the transcript and generate structured notes.

"Action items only"

Extract just the action items table — skip everything else.

"What did [person] commit to?"

Filter action items for a specific person.

"Follow up on last meeting"

Load the most recent meeting notes from ~/.openclaw/meetings/ and show overdue action items.

"Standup notes"

Shorter format for daily standups:

# Standup — [Date]

## [Person 1]
- Yesterday: [what they did]
- Today: [what they'll do]
- Blockers: [any blockers]

## [Person 2]
...

Meeting Log

Save all meeting notes to ~/.openclaw/meetings/[date]-[topic].md

When asked "show past meetings" or "meeting history":

# Meeting History

| Date | Topic | Action Items | Status |
|------|-------|-------------|--------|
| Mar 27 | Sprint planning | 5 items | 3 done, 2 pending |
| Mar 25 | Design review | 3 items | all done |
| Mar 20 | Dr. Wu check-in | 4 items | 1 overdue |

Read the full file on GitHub · 123 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 123 lines · 74 tokens per session scan A 8d3a7c99902f

Subscribe to this mod's changes

meeting-notes is a skill published in the GitHub repository vanthienha199/openclaw-skills (1 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 837 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.