agentleFS
pholbopholbo/getting-things-adhdone/skills/prep-meeting/SKILL.md

prep-meeting

Skill7 starsChanged 49 days agoMITView on GitHub

Given a meeting name/topic for today (you name it - no calendar read access), finds or creates a dated meeting note and populates it with matching tasks pulled by tag from your task manager. Links the note into today's Daily note. Standalone, or run once per meeting from start-the-day. Trigger: /prep-meeting, or naming a meeting you want to prep for.

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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a dated meeting note already exists for today, open it and add the task list plus anything else worth raising.

    line 46
  2. Distinctive:

    If not, create one following your standard note template's frontmatter shape rather than inventing a new one, named descriptively (e.g.

    line 48
  3. Very specific:

    Link it from the Daily note: Add (or append to) a ## Meetings today section in today's Daily note with a wikilink to the meeting note.

    line 53
  4. Distinctive:

    Never edit the task manager, never invent new tasks, never reorganise unrelated parts of the meeting note or Daily note.

    line 62
  5. Distinctive:

    Don't guess the day's schedule - the user names the meeting.

    line 64

“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

Purpose

Pull together what's relevant for a specific meeting today - existing notes, plus any outstanding tasks tagged for that client/person in your task manager - without having to hunt across the vault and the task manager yourself.

Trigger

/prep-meeting, or naming a meeting you want to prep for. Also invoked once per named meeting by /start-the-day.

Process

  1. Work out what kind of meeting it is - a topic tied to an existing standing note (a client, project, or similar), a recurring 1:1 with a person, or something else.
  2. Search the vault for an existing dated meeting note covering today's meeting specifically (a YYYY-MM-DD Meeting - <topic/person>.md pattern works well), plus the standing note it relates to.
  3. Pull relevant tasks by tag, if your task manager's tags overlap with vault topics/people. Pull a full-detail export from your task manager (see skills/things3-export/ for an example Things3 integration - don't substitute a trimmed-down snapshot note here, it may be missing the tags field this step depends on). Filter for items whose tags match, and add them to the note as a plain bulleted list of outstanding items. If nothing's tagged yet for this client/person, say so rather than guessing. (Task-manager tags don't have to follow the same convention as your vault's Obsidian tags - the author's, for instance, uses Title Case with spaces in Things3 while the vault stays flat and lowercase; match whatever the mapping actually is for you.)
  4. Populate the note.
    • If a dated meeting note already exists for today, open it and add the task list plus anything else worth raising.
    • If not, create one following your standard note template's frontmatter shape rather than inventing a new one, named descriptively (e.g. YYYY-MM-DD Meeting - <topic/person>.md), filed wherever fits your folder structure (a client/project folder for topic-driven meetings, alongside existing dated notes for a recurring 1:1).
  5. Link it from the Daily note. Add (or append to) a ## Meetings today section in today's Daily note with a wikilink to the meeting note. Create the section if it doesn't exist yet; don't duplicate a link that's already there. If the Daily note itself doesn't exist yet, this is normally handled by whatever called this skill (e.g. start-the-day) - create it only if nothing else will.

Guardrails

  • Never edit the task manager, never invent new tasks, never reorganise unrelated parts of the meeting note or Daily note.
  • Don't guess the day's schedule - the user names the meeting; there's no calendar read access.

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.