meeting-notes

meeting-notes is a skill for Claude Code, Codex from jezweb/vite-flare-starter. It costs 59 tokens per session (672 once invoked), scanned A, original, MIT.

A workflow for turning a meeting audio recording into structured Markdown notes. It extracts attendees, discussion topics, decisions, assigned actions, and unresolved questions.

In plain words
What is it for?
Transcribing a meeting recording, summarizing what was discussed, recording decisions and owners, and saving the results as a notes file.
Why use it?
It removes the need to listen through a recording and organize the meeting information manually.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Transcribing a meeting recording, summarizing what was discussed, recording decisions and owners, and saving the results as a notes file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jezweb/vite-flare-starter/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 jezweb/vite-flare-starter --skill meeting-notes
Clone the repo
git clone --depth 1 https://github.com/jezweb/vite-flare-starter

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/jezweb/vite-flare-starter/meeting-notes/github.svg)](https://agentmods.dev/skills/jezweb/vite-flare-starter/meeting-notes)
Your own site
<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/meeting-notes"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/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/jezweb/vite-flare-starter/meeting-notes"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/meeting-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 672 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00059 $0.00672
Opus 5 $0.00030 $0.00336
Sonnet 5 $0.00012 $0.00134
Haiku 4.5 $0.00006 $0.00067

Measured 10d ago against content hash 2c3818b974f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 10d 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.

skills/meeting-notes/SKILL.md · 55 lines

How it starts

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

Meeting notes from audio

When to use

The user provides a meeting recording (audio file attachment or an existing audio file in their filesystem) and wants structured notes — not a verbatim transcript.

Examples:

  • "Summarise this meeting recording"
  • "Get me the action items from this call"
  • "Turn [audio.mp3] into meeting notes"

Steps

  1. Transcribe. Call transcribe_audio with the audio source (attachment bytes or file path). The tool auto-detects language.

  2. Structure the notes. Write a concise markdown document with these sections. Omit sections that have no content — don't leave empty headings.

    • # {Title or "Meeting notes"} — {date}
    • ## Attendees — names mentioned; mark ones you're unsure about with (?)
    • ## Summary — 2-3 sentences: what was the meeting for, what got decided
    • ## Discussion — bullet list of the main topics covered, one line each
    • ## Decisions — numbered list of concrete decisions with context
    • ## Action items- [ ] {action} — {owner} ({due date if mentioned})
    • ## Open questions — things raised but not resolved
    • ## Follow-ups — items deferred to a future meeting
  3. Save to the user's filesystem. Call fs_write with path: "meetings/{YYYY-MM-DD}-{slug}.md" and the content. Use today's date unless the meeting clearly happened on a different day (mentioned in the audio).

  4. Show the result inline. Render the notes in chat so the user can scan them without opening the file. Add a note of where you saved it (users/<you>/meetings/...).

  5. Offer follow-ups. Use offer_choices:

    • "Email me these notes"
    • "Generate a Word doc from this"
    • "Add action items to my todo list"
    • "Extract decisions as a CSV"

Style

  • Prefer paraphrasing over verbatim quotes — meeting notes are summaries.
  • Use tense consistent with the meeting (past for decisions, present for action items).
  • Be specific about owners — "Jez" is better than "someone".
  • If a dollar figure, date, or number is mentioned, include it exactly.
  • Action items as checkboxes so the user can tick them off directly.

Read the full file on GitHub · 55 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. 10d ago First seen · 55 lines · 59 tokens per session scan A 2c3818b974f1

Subscribe to this mod's changes

meeting-notes is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 15d ago), licensed MIT. It adds 59 tokens to every session and 672 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

baoyu-youtube-transcript

A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.

JimLiu/baoyu-skills · 107 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

read

Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…

tw93/Waza · 78 tokens

overleaf-sync

A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.

wanshuiyin/Auto-claude-code-research-in-sleep · 97 tokens