prep-meeting
Skill9 starsChanged 8 months agoMITView on GitHub
General meeting preparation — loads context, compiles topics, creates a prep note. Use for any meeting. Trigger on phrases like "prepare meeting", "prep meeting", "meeting vorbereiten", or "preparation for [meeting name]".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- pholbo/getting-things-adhdonetheir own version, first seen Nov 12, 2026
- cobusgreyling/grok-bot-templatestheir own version, first seen Aug 29, 2026
- alejopijuan/Claude-Code-Agency-Co-Foundertheir own version, first seen Jul 9, 2026
- breethomas/bette-ostheir own version, first seen Mar 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- cobusgreyling/grok-bot-templates★ 14same name
- pholbo/getting-things-adhdone★ 11same name
- breethomas/bette-os★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-commandSkill
- daily-reviewSkill
- de-aiifySkill
- inbox-processorSkill
- morning-planSkill
- process-meetingSkill
- research-assistantSkill
- setupSkill
- thinking-partnerSkill
- weekly-synthesisSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Templates: Always read 04_RESOURCES/Templates/Meeting Preparation.md before creating a note
- Distinctive: line 20
WikiLinks: NEVER wrap [[WikiLinks]] in backticks
- Very specific: line 21
File placement: Follow the folder routing table below — NEVER save directly in 03_AREAS/Meetings/
- Distinctive: line 22
No speculation: Only add topics you have evidence for (hub file, daily note, previous meeting note)
- Distinctive: line 30
If the user gave enough context (e.g.
- Distinctive: line 31
If unclear, ask: "Which meeting, with whom, and on what date?"
- Distinctive: line 41
Run all relevant reads in parallel:
- Distinctive: line 68
Keep topics concise: one line each.
- Very specific: line 74
Create the file using the template.
- Very specific: line 82
CRITICAL —
## Meeting Documentationsection: Leave completely untouched with template placeholders.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prep Meeting Skill
Prepares you for any upcoming meeting by loading relevant context, compiling topics
to address, and creating a structured prep note. The note is intentionally lightweight —
Notes and Tasks are filled after the meeting via /process-meeting.
CRITICAL RULES
- Templates: Always read
04_RESOURCES/Templates/Meeting Preparation.mdbefore creating a note - WikiLinks: NEVER wrap [[WikiLinks]] in backticks
- File placement: Follow the folder routing table below — NEVER save directly in
03_AREAS/Meetings/ - No speculation: Only add topics you have evidence for (hub file, daily note, previous meeting note)
Step 1 — Identify the meeting
Determine: which meeting, which date, which attendees.
If the user gave enough context (e.g. "prep for team standup with Dennis tomorrow"), confirm and proceed. If unclear, ask: "Which meeting, with whom, and on what date?"
Once identified, determine:
- Meeting type: 1:1 with direct report / 1:1 with peer / 1:1 with leadership / team meeting / external / other
- Attendees: list of names
Step 2 — Load context
Run all relevant reads in parallel:
- Hub files — for each attendee who has a hub file, read it from
03_AREAS/People/:- Direct reports:
03_AREAS/People/Team/[Name]/[Name].md - Peers:
03_AREAS/People/Peers/[Name]/[Name].md - Leadership:
03_AREAS/People/Leadership/[Name]/[Name].md - Extract: 📌 Next Meeting items, open tasks (👥 / ⌛), Focus Topics
- Direct reports:
- Daily Note — read
01_ACTIVE/Daily Notes/YYYY-MM-DD.md- Extract: any 📌 @[attendee] items relevant to this meeting
- Previous meeting note — glob
03_AREAS/**/*[Name or MeetingKeyword]*.mdfor the most recent note of this recurring meeting type- Extract: open action items, unresolved topics
- Meeting Preparation template — read
04_RESOURCES/Templates/Meeting Preparation.md
Step 3 — Compile "My Topics & Questions"
From all loaded context, compile a deduplicated list of topics to raise:
- 📌 items from hub files and daily note (primary source)
- Open tasks or waiting-for items that need a status update
- Unresolved items from the previous meeting note
- Any context the user provided in the prompt
Keep topics concise: one line each. No invented items.
Step 4 — Create the prep note
Create the file using the template. Fill in only the ## Meeting Preparation section:
- Frontmatter: apply standard meeting frontmatter
- Header: date + meeting name
- Meeting Date / Type / Attendees: fill from Step 1
- My Topics & Questions: insert compiled topics as a prioritized bullet list
- Open Tasks & Delegations: pull from hub file tasks section
CRITICAL — ## Meeting Documentation section: Leave completely untouched with template placeholders. These are filled after the meeting via /process-meeting.
Frontmatter:
---
tags: [meeting, preparation, YYYY-MM-DD]
up: "[[folder-path]]"
---File naming: YYYY-MM-DD_[Meeting-Name].md
Folder routing:
| Meeting type | Folder |
| 1:1 with direct report | 03_AREAS/People/Team/[Name]/ |
| 1:1 with peer | 03_AREAS/People/Peers/[Name]/ |
| 1:1 with leadership | 03_AREAS/People/Leadership/[Name]/ |
| Recurring team meeting | 03_AREAS/Organization/[MeetingType]/ |
| General / external | 03_AREAS/Organization/ |
Step 5 — Summary
Tell the user briefly:
- File created at [path]
- How many topics are queued
- The 1–2 most important topics to not skip (your judgment based on context)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

