meeting-prep

meeting-prep — Pre-Meeting Brief

Produces a one-page markdown brief so you walk into meetings knowing what's going on.

Output shape

## Meeting: {title}
**When:** {datetime} · **Duration:** {duration} · **Where:** {location}
**Attendees:** {list with titles where known}

### Context
- Last topic we discussed: {summary}
- Open asks from them: {list}
- Open asks from me: {list}

### Likely agenda
1. {item}
2. {item}

### My position / notes
{bulleted; pulled from memory if relevant}

### Warnings
- {anything they sent recently that suggests a tough topic}

### Quick links
- [last email thread]({url})
- [shared doc]({url})
- [previous meeting notes]({memory-link})

Procedure

1. Resolve meeting from lookup::

   • "next" → next calendar event in personal calendar
   • a time → nearest event at that time
   • a person → next event where that person is an attendee
   • event id → that exact event

2. Gather (parallel):

   • Last 10 emails with each attendee (last 90 days)
   • Last Slack DMs / channel mentions with each attendee (last 30 days)
   • Relevant docs from memory (/search with meeting title + attendee names)
   • Previous meeting notes if exist in memory

3. Summarize each thread to 1–2 lines. Extract open asks (things needing response, either direction).

4. Produce the brief. Keep under 400 words. Bias for brevity — this is a read-in-60-seconds doc.

5. Attach the brief as a Telegram DM reply to the trigger event, or print to CLI if invoked there.

Triggering 15 min before each meeting

Cron jobs live in ~/.hermes/cron/jobs.json, created via hermes cron create. The old YAML cron list (and its filter: field) was removed upstream — the cheapest honest pattern is a short-interval job that runs the skill and lets it decide whether a meeting is <15m away (the skill queries your calendar anyway):

hermes cron create "*/5 * * * *" \
  "Prep for the next meeting if it starts within 15 minutes and is tagged prep:true" \
  --skill meeting-prep --name meeting-prep --deliver telegram