meet

meet is a skill for Claude Code, Codex from kv0906/pm-kit. It costs 30 tokens per session (640 once invoked), scanned A, original, MIT.

A meeting-notes workflow that turns raw notes into a structured record. It identifies decisions, blockers, tasks, attendees, and details such as the project and meeting type.

In plain words
What is it for?
Use it to process pasted notes, create a meeting note, record decisions and blockers, extract action items, and link the resulting notes.
Why use it?
It reduces the work of rereading notes and manually finding the commitments and unresolved issues hidden in them.

Skill for Claude CodeCodex

Part of the pm-kit plugin — 35 skills, 7 agents, 2 hooks shipped together

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.

agentmods
npx agentmods add skills/kv0906/pm-kit/meet
Any agent
npx skills add kv0906/pm-kit --skill meet
Clone the repo
git clone --depth 1 https://github.com/kv0906/pm-kit

Made for: Claude Code, Codex.

Or install pm-kit, the plugin that ships this one along with the rest of its 35 skills, 7 agents, 2 hooks.

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 meet

README.md
[![agentmods](https://agentmods.dev/badge/skills/kv0906/pm-kit/meet.svg)](https://agentmods.dev/skills/kv0906/pm-kit/meet)
Your own site
<a href="https://agentmods.dev/skills/kv0906/pm-kit/meet"><img src="https://agentmods.dev/badge/skills/kv0906/pm-kit/meet.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 640 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00030 $0.00640
Opus 5 $0.00015 $0.00320
Sonnet 5 $0.00006 $0.00128
Haiku 4.5 $0.00003 $0.00064

Measured 3d ago against content hash 88e491e71eb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

meet 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 3d 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/meet/SKILL.md · 87 lines

How it starts

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

/meet — Meeting Processing

Process raw meeting notes into structured notes with extracted decisions, blockers, and action items.

Context

Today's date: !date +%Y-%m-%d Recent meetings: !ls meetings/*.md 2>/dev/null | tail -5

Reference template: @_templates/meeting.md Config: @_core/config.yaml Processing logic: @_core/PROCESSING.md

Input

User input: $ARGUMENTS

Then user will paste raw notes.

Session Task Progress

TaskCreate: "Parse meeting metadata"
  activeForm: "Parsing meeting metadata..."

TaskCreate: "Extract decisions, blockers, actions"
  activeForm: "Extracting items from notes..."

TaskCreate: "Create linked notes"
  activeForm: "Creating linked notes..."

Processing Steps

  1. Parse Input

    • Extract project
    • Extract type: sync, milestone, external
    • Generate slug from title
  2. Request Notes

    • If notes not provided, prompt: "Paste your meeting notes:"
  3. Extract from Notes

    • Decisions: Look for "decided", "agreed", "going with"
    • Blockers: Look for "blocked", "stuck", "waiting on"
    • Action Items: Look for "will do", "action:", "TODO", "@name"
    • Attendees: Look for @mentions or name lists
  4. Create Meeting Note

    • Filename: meetings/{date}-{type}-{slug}.md
    • Apply template with extracted data
    • Add ## Links section
  5. Create Linked Notes

    • For each decision: Create decisions/{project}/{date}-{slug}.md
    • For each blocker: Create blockers/{project}/{date}-{slug}.md
    • Link back to meeting note
  6. Update References

    • Add to project index if exists
  7. Append to Vault Log

    • Append entry to 01-index/_vault-log.md (see .claude/rules/vault-log.md)
    • Action: meeting
    • Details: summarize what was extracted (decisions, blockers, action items)

Output

Created: meetings/{date}-{type}-{slug}.md
Extracted:
- Decisions: {count} (notes created)
- Blockers: {count} (notes created)
- Action items: {count}

Export (Optional)

Read the full file on GitHub · 87 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. 3d ago First seen · 87 lines · 30 tokens per session scan A 88e491e71eb0

Subscribe to this mod's changes

meet is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 640 once invoked, about $0.0002 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

critique-agent

Pressure-test an existing product brief or PRD pack — find gaps, hidden assumptions, inconsistencies, and failure modes before stakeholder review. Use when: critique brief, critique PRD, devils advocate, red team, pressure test, find holes, what could go wrong, stress test the doc, pre-mortem.

ertra/pm-brain-for-cursor · 69 tokens

interview-frameworks

Frameworks for user interviews, question design, and qualitative research. Use when conducting user interviews, designing interview guides, researching user needs, or gathering qualitative insights. Trigger on: 'create an interview guide', 'how do I interview users', 'customer discovery questions', 'user research…

ertra/pm-brain-for-cursor · 69 tokens

query-datasets

Answer grounded yes/no questions about what exists in the 03-datasets/ example corpora (supporttickets, calltranscripts) using the local SQLite + FTS5 + vector hybrid index. Use when the user asks 'do/does [corpus] contain/mention/include/have requests for X?', 'any [corpus] about Y?', or similar factual queries over…

ertra/pm-brain-for-cursor · 91 tokens

critique-prd

Rubric-score a PRD pack (02 + 03) against the 7-dimension PM Brain rubric and run a 4-persona panel review. Returns scores, panel critiques, the single weakest section, a concrete rewrite, and P0/P1 fix lists. Use when: PRD review, score my PRD, rubric review, panel review, rewrite weakest section, critique-prd.

ertra/pm-brain-for-cursor · 86 tokens

create-prd

Write the PRD pack (02-product-requirements.md + 03-success-metrics.md) on top of an approved product brief. Use when: PRD, product requirements, requirements doc, success metrics, spec writeup, shape the PRD.

ertra/pm-brain-for-cursor · 56 tokens

create-internal-feature-announcement

Drafts an internal feature announcement (IFA) from the PRD pack and user sources using the repo template, then writes 04-internal-feature-announcement.md. Use when: IFA, internal feature announcement, internal FAQ, Slack IFA prep, launch comms pack, or internal product documentation from the template.

ertra/pm-brain-for-cursor · 71 tokens