agentleFS
timominkustimominkus/obsidian-para-gtd-ai/.claude/skills/prep-meeting/SKILL.md

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

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
  1. Very specific:

    Templates: Always read 04_RESOURCES/Templates/Meeting Preparation.md before creating a note

    line 19
  2. Distinctive:

    WikiLinks: NEVER wrap [[WikiLinks]] in backticks

    line 20
  3. Very specific:

    File placement: Follow the folder routing table below — NEVER save directly in 03_AREAS/Meetings/

    line 21
  4. Distinctive:

    No speculation: Only add topics you have evidence for (hub file, daily note, previous meeting note)

    line 22
  5. Distinctive:

    If the user gave enough context (e.g.

    line 30
  6. Distinctive:

    If unclear, ask: "Which meeting, with whom, and on what date?"

    line 31
  7. Distinctive:

    Run all relevant reads in parallel:

    line 41
  8. Distinctive:

    Keep topics concise: one line each.

    line 68
  9. Very specific:

    Create the file using the template.

    line 74
  10. Very specific:

    CRITICAL — ## Meeting Documentation section: Leave completely untouched with template placeholders.

    line 82

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md before 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:

  1. 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
  2. Daily Note — read 01_ACTIVE/Daily Notes/YYYY-MM-DD.md
    • Extract: any 📌 @[attendee] items relevant to this meeting
  3. Previous meeting note — glob 03_AREAS/**/*[Name or MeetingKeyword]*.md for the most recent note of this recurring meeting type
    • Extract: open action items, unresolved topics
  4. 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 typeFolder
1:1 with direct report03_AREAS/People/Team/[Name]/
1:1 with peer03_AREAS/People/Peers/[Name]/
1:1 with leadership03_AREAS/People/Leadership/[Name]/
Recurring team meeting03_AREAS/Organization/[MeetingType]/
General / external03_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)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.