Meeting Prep

For your AI

Share this page with Claude. It reads the definition below, creates the folders, instructions, tags, and starter notes in your account.

---
name: Meeting Prep
description: 'Your AI reads your calendar, searches your notes, and briefs you before
  every meeting. After, describe what happened and it saves the decisions, action
  items, and context — linked to everything you already know.

  '
tags:
- meeting
- briefing
containers:
- name: Meeting Prep
  description: Meeting briefings and notes
  llm_instructions: |
    Read the "Meeting Prep Guidelines" note in this container before creating or updating any notes. Always search all notes, not just this folder.

    Briefing workflow (before a meeting):
    1. Search all notes for anything related — the people, the topic, the project, the company.
    2. Create a note titled "Briefing: [Topic] — YYYY-MM-DD", tag with "briefing".
    3. Sections:
       **Meeting** — title, time, attendees, agenda (whatever is known).
       **Context** — what you found, summarized with links. Past meetings, related notes, open action items.
       **Talking points** — what the user should raise or follow up on.
    4. Bullet points only. If nothing relevant exists, say so.

    Capture workflow (after a meeting):
    1. The user describes what happened — voice dump, bullets, one sentence. Extract the signal, discard the raw input.
    2. Create a note titled "Meeting: [Topic] — YYYY-MM-DD", tag with "meeting".
    3. Sections (omit any that have nothing):
       **Attendees** — who was there.
       **Summary** — 2-4 sentences on what was discussed and the outcome.
       **Decisions** — specific decisions, each as a bullet.
       **Action items** — "- [ ] Owner: Task (due date)".
    4. Link to the briefing if one exists. Search for previous meetings on the same topic or with the same people and link to them.
    5. If the meeting produced information that should update a note elsewhere, suggest it.

    Rules:
    - Do not invent details. If something is ambiguous, omit it.
    - Search for existing notes on the same meeting before creating. Update instead of duplicating.
    - Link notes with wiki-style references. Meetings link to briefings. Follow-ups link to prior meetings.
    - When attendees are named, search for notes about them. If none exist, say so — do not create People notes.
  notes:
  - title: Meeting Prep Guidelines
    body: |
      Your AI reads this before creating briefings or meeting notes.

      **Before a meeting — say something like:**
      - "Brief me for my 2pm with Sarah"
      - "What meetings do I have tomorrow?"
      - "I have a call with Acme Corp about the pilot program, here's the agenda: ..."

      Your AI searches all your notes for anything related — past meetings, project context, open action items — and creates a briefing with talking points.

      **After a meeting — say something like:**
      - "Just got out of the Q3 planning call. We decided to push launch to May. I need to update the roadmap by Friday, Sarah handles customer comms."
      - "Met with the design team, notes: ..."

      Your AI saves a note with attendees, decisions, and action items. It links back to the briefing and to previous meetings on the same topic.

      Edit this note to match how you work.
    tags:
    - meeting
    container_path: Meeting Prep