What is process-meeting?

A meeting-processing workflow that turns a transcript, summary, photo of a whiteboard, or raw notes into a structured record. It extracts decisions, tasks, and information about people or projects, then places each item where it can be found later.

Use it after meetings and one-to-ones to capture decisions, assign follow-ups, record project or people signals, and update the relevant notes.

It prevents important outcomes from being buried in a transcript or forgotten after the meeting. Recording each result in its proper location makes it available to later work.

process-meeting — Skill for Claude Code by pe-menezes

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 pe-menezes/pm-chief-of-staff --skill process-meeting

Clone the repo

git clone --depth 1 https://github.com/pe-menezes/pm-chief-of-staff

Made for: Claude Code.

Or install pm-chief-of-staff, the plugin that ships this one along with the rest of its 12 skills, 1 agent, 4 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pe-menezes/pm-chief-of-staff/process-meeting/github.svg)](https://agentmods.dev/skills/pe-menezes/pm-chief-of-staff/process-meeting)

Your own site

<a href="https://agentmods.dev/skills/pe-menezes/pm-chief-of-staff/process-meeting"><img src="https://agentmods.dev/badge/skills/pe-menezes/pm-chief-of-staff/process-meeting/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pe-menezes/pm-chief-of-staff/process-meeting"><img src="https://agentmods.dev/badge/skills/pe-menezes/pm-chief-of-staff/process-meeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,233 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.

Model	Per session	Once invoked
Fable 5.1	$0.00124	$0.01233
Opus 5.5	$0.00050	$0.00493
Sonnet 5.5	$0.00025	$0.00247
Haiku 4.5	$0.00012	$0.00123

Measured 3d ago against content hash 98bb2016b3e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

process-meeting 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.

seeds/process-meeting/SKILL.md · 70 lines

How it starts

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

Process a meeting

pm-chief-of-staff seed. This file is YOURS: ask the agent to change the note format or the propagation rules and it edits this skill on the spot.

Writing: write to the person and in their files in the language this folder's instruction file defines (the AGENTS.md; in a folder without AGENTS.md, the CLAUDE.md); without one, in the language the person writes in, and fallback questions go in their language too. Follow that file's writing canon. Without it: no em dash (use a comma, parentheses or a colon), short dense sentences, 1 line per item.

The value lies in extracting what changes the state of the system (decision, task, signal about a person or project) and putting each thing in the place where it will be found. One meeting processed and propagated is worth more than ten stored transcripts.

Step 1: receive the material

Accept any form: pasted transcript, automatic summary (Gemini, Zoom, Granola), photo of a whiteboard, raw typed notes. Ask only what cannot be inferred: who it was with and when (if it is not in the material).

If .claude/skills/_shared/capabilities.md exists with provider and how to call filled in on the meeting transcript line, offer to fetch the transcript through there instead of waiting for pasted material. Without the module, with the line half-filled, or with no result from the fetch, go on with what the person pastes.

A transcript proves only what was SAID: a relevant factual claim that exists only in speech goes into the note marked as "to validate".

Step 2: write the note

File at meetings/{person-or-ritual}/YYYY-MM-DD.md, aiming at 25 lines at most. The raw text (transcript, automatic summary) NEVER goes into the operational vault: kept in here, it becomes a distractor for every future search. The note is the distillate + 1 pointer line to where the raw text lives (a cold folder outside the vault, a drive, or the source itself). The skill does not move or delete the raw text: the person decides where it stays.

Read the full file on GitHub · 70 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.

3d ago Changed 98bb2016b3e4
7d ago First seen · 70 lines · 124 tokens per session scan A 700f76e33354

Subscribe to this mod's changes

process-meeting is a skill published in the GitHub repository pe-menezes/pm-chief-of-staff (5 stars, last pushed 3d ago), licensed MIT. It adds 124 tokens to every session and 1,233 once invoked, about $0.0005 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-10-31.

Claude Code Memory and context Project management chief-of-staff claude-code-plugin codex product-management second-brain

process-meeting next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
process-meetingpe-menezes/pm-chief-of-staff	Skill	5	3d ago	MIT	A	124	Claude Code
rethinkagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	51	Claude Code
graphagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	50	Claude Code
rememberagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	40	Claude Code
seedagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	49	Claude Code
migrateguhcostan/claude-mega-brain	Skill	127	3mo ago	MIT	A	147	Claude Code
claude-mega-brainguhcostan/claude-mega-brain	Skill	127	3mo ago	MIT	A	96	Claude Code