Write a one-page prep note before a meeting from what the vault already knows: previous notes, open commitments on both sides, open questions, goals, questions to ask, a proposed agenda. Use when the person says "prepare me for the meeting", "where did we leave it with", "what do I need to know before the call", "make an agenda".
Installs into .claude/skills of the current project.
Are you the author of Meeting Prep?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/exarlabs-meeting-prep)
---
name: meeting-prep
description: Write a one-page prep note before a meeting from what the vault already knows: previous notes, open commitments on both sides, open questions, goals, questions to ask, a proposed agenda. Use when the person says "prepare me for the meeting", "where did we leave it with", "what do I need to know before the call", "make an agenda".
---
# meeting-prep
Thin entry (PAROS P04). The knowledge lives in a live definition; this file only finds it.
1. Locate the live definition, first match wins:
- where the vault entry file (`AGENTS.md` or `CLAUDE.md`) says skills live: `<skills folder>/meeting-prep/CURRENT.md`;
- `<vault>/PAROS/skills/meeting-prep/CURRENT.md`;
- the PAROS reference copy: `<paros repo>/packs/meetings/meeting-prep/CURRENT.md`.
2. Read it in full, and the `LOCAL.md` next to it if present (your areas, folders and rules). Read its `version:` field.
3. Report one line before working:
- from the vault: `Running meeting-prep v<X> from your vault`;
- from the reference copy: `Running meeting-prep v<X> from the PAROS reference, not yet adopted`.
4. Follow it. The meetings pack overview is in `packs/meetings/README.md`. Its `## Constitution` always wins.
5. If the person corrects the result, write a learning packet to the skill's `observations/` folder (P05).
