What is prep-conversation?

A conversation-preparation workflow that builds an agenda from existing notes about a person and recent meetings. An agenda is a list of topics and follow-ups for a meeting.

Use it before a one-to-one with a direct report, manager, colleague, or stakeholder to gather relevant facts, review recent follow-ups, and prepare discussion topics.

It avoids relying on memory or creating a generic meeting list. The person validates the proposed topics before they become the final agenda.

prep-conversation — 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 prep-conversation

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/prep-conversation/github.svg)](https://agentmods.dev/skills/pe-menezes/pm-chief-of-staff/prep-conversation)

Your own site

<a href="https://agentmods.dev/skills/pe-menezes/pm-chief-of-staff/prep-conversation"><img src="https://agentmods.dev/badge/skills/pe-menezes/pm-chief-of-staff/prep-conversation/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/prep-conversation"><img src="https://agentmods.dev/badge/skills/pe-menezes/pm-chief-of-staff/prep-conversation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,033 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.00135	$0.01033
Opus 5.5	$0.00054	$0.00413
Sonnet 5.5	$0.00027	$0.00207
Haiku 4.5	$0.00014	$0.00103

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

Security

Grade A, and why

prep-conversation 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 7d 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/prep-conversation/SKILL.md · 56 lines

How it starts

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

Prep a conversation

pm-chief-of-staff seed. This file is YOURS: ask the agent to change the agenda format ("I want it to always have a section for X") 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.

A good agenda is born from what is already written. The flow: gather candidates → validate with the person → write the agenda with only what was validated.

Step 1: gather candidates

Read the person's hub in people/, starting from the top: the Facts section (dated, with source) and the Current reading (the most recent, with no "superseded on YYYY-MM-DD by" mark) are the base of the prep; a reading marked as superseded is ignored. Recent signals and History come in as a complement.
Read the last 2 to 3 notes of conversations with them in meetings/: what was left as a follow-up (on both sides), what was agreed "for next time".
Grep the name in the journal and in memory/ for the last 2 weeks: what came up about them or about their topics.
Every item in the hub's "Recent signals" section is a candidate. A signal sitting for more than 3 weeks comes in with the question: chase it again, or did it drop?
If .claude/skills/_shared/capabilities.md exists with provider and how to call filled in on messages or tickets, pull through there what came up in the last 2 weeks about the person and their topics (the same window as item 3), as a candidate like the others. Without the module, with the line empty or half-filled, or if the fetch fails, step 1 stays in the files, which is the default.

Step 2: validate with the person

Present the candidates numbered, grouped (open follow-ups / signals / new topics), and ask what goes in: take / not today / drop / edit. Do not censor a candidate on your own; the person decides.

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

7d ago First seen · 56 lines · 135 tokens per session scan A 337e7e01f2aa

Subscribe to this mod's changes

prep-conversation is a skill published in the GitHub repository pe-menezes/pm-chief-of-staff (5 stars, last pushed 3d ago), licensed MIT. It adds 135 tokens to every session and 1,033 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 Planning Project management chief-of-staff claude-code-plugin codex product-management second-brain

prep-conversation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
prep-conversationpe-menezes/pm-chief-of-staff	Skill	5	3d ago	MIT	A	135	Claude Code
reduceagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	73	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
nextagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	50	Claude Code
ralphagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	61	Claude Code
rememberagenticnotetaking/arscontexta	Skill	3.5k	8mo ago	MIT	A	40	Claude Code