meeting-analyzer

meeting-analyzer is a skill for Claude Code from hamzafarooq/claude-code-starter. It costs 39 tokens per session (263 once invoked), scanned A, original, MIT.

A workflow for reading meeting notes or transcripts and identifying decisions, action items, risks, and unanswered questions.

In plain words
What is it for?
It is for analyzing stand-ups, planning meetings, design reviews, one-to-ones, and other recorded discussions.
Why use it?
It turns unstructured meeting records into a clearer list of what was agreed, what must happen next, and what still needs discussion.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit It is for analyzing stand-ups, planning meetings, design reviews, one-to-ones, and other recorded discussions.

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

Made for: Claude Code.

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-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/meeting-analyzer/github.svg)](https://agentmods.dev/skills/hamzafarooq/claude-code-starter/meeting-analyzer)
Your own site
<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/meeting-analyzer"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/meeting-analyzer/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-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/meeting-analyzer"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/meeting-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 263 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.00039 $0.00263
Opus 5.5 $0.00016 $0.00105
Sonnet 5.5 $0.00008 $0.00053
Haiku 4.5 $0.00004 $0.00026

Measured 1mo ago against content hash 9b0dc3715ff6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

meeting-analyzer 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 1mo 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.

.claude/skills/meeting-analyzer/SKILL.md · 38 lines

What it actually says

Ask the user to paste their meeting notes or transcript.

Then return:

Meeting Analysis

Meeting type: [standup / planning / design review / 1:1 / exec review / other] Date: [if mentioned] Attendees: [if mentioned]


Decisions Made

Bullet list of things that were agreed or resolved. Flag HIGH CONFIDENCE vs TENTATIVE.

Action Items

Owner Task Due date
[name or "unassigned"] [specific action] [date or "not set"]

Open Questions

Things raised but not resolved. These need a follow-up owner.

Risks & Blockers

Anything that could slow progress. One sentence each.

What Was Left Unsaid

One observation about what the notes suggest but no one said directly — a tension, an assumption, or a decision that needs to be made but wasn't.


Keep the action items actionable: verb + object + owner. If the notes are vague, flag it rather than fabricate specificity.

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. 1mo ago First seen · 38 lines · 39 tokens per session scan A 9b0dc3715ff6

Subscribe to this mod's changes

meeting-analyzer is a skill published in the GitHub repository hamzafarooq/claude-code-starter (145 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 263 once invoked, about $0.0002 per session on Opus 5.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-09-03.