Meeting transcripts

Every meeting your notes tool records becomes a list entry, kept current by a routine, with re-runs that update rather than duplicate.

You get a list where every meeting is one named entry with its transcript as the body and the source id in its structured data, kept current by a routine that picks up new and edited meetings.

The prompt

Read the skill at https://github.com/fred-abrahamson/midland-examples/blob/main/meeting-transcripts/SKILL.md and follow it. Source: our meeting notes provider's API, credential "meetings". Destination: the list "Meeting transcripts". Every 30 minutes. One entry per meeting named "<title> — <date>", keyed by the provider's note id, cursor on updated_at. Preview against the last week and stop before activating.

The skill

meeting-transcripts/SKILL.md covers the list-then-detail fetch with pagination, the key and the cursor, and fixtures for an empty result, two pages and a changed meeting. It ends with the authoring guide the list carries.

Check

The preview lists one write per meeting from the last week with no duplicates. Activate. Edit a meeting’s title at the source; the next attempt shows one update, not a new entry.