Connectors
This plugin bundles no connectors. It names the category of tool it needs and works with whichever one you have connected. In the skill files, two tildes mark a placeholder: ~~task board means "whatever you use for this."
| Category | Placeholder | Options | Required |
|---|---|---|---|
| Transcription | ~~transcription | Otter, Zoom, Fathom, Granola, or a transcript file | Yes |
~~email | Gmail, Outlook, Microsoft 365 | Optional | |
| Calendar | ~~calendar | Google Calendar, Outlook Calendar | Optional |
| Document store | ~~document store | Google Drive, SharePoint, a local folder | Optional |
| Task board | ~~task board | Notion, Todoist, Asana, ClickUp, Linear | Optional |
If a category is not connected
Nothing breaks. Each skill falls back to a file in the engagement folder. No ~~email: the recap is written as a file to copy out. No ~~calendar: next-session facts are recorded and flagged as unbooked. No ~~task board: commitments stay in the state file.
The only hard requirement is a transcript.
One rule about transcription tools
Transcription tools produce a summary alongside the transcript. Never read it, never quote it, never let it stand in for the transcript. Otter's summary of the 2026-08-12 Saunders session reported "Steven acquiring 30% by 2027 and Bev retaining 70%" as settled. The transcript says the gifting schedule is settled and the purchase is not, because Steven has not calculated the debt service. A summary flattens modality. That flattening is the single most expensive error this plugin exists to prevent.
Document stores
A mounted network drive (G:) exists on the machine that maps it and nowhere else. A cloud session has no G: at all — check before the first write, and if it is unreachable, say so rather than falling back to a connector, which writes by parent ID rather than path and converts to Google-native types by default.
Destinations are resolved before the write, never after. Not because a misplaced file cannot be corrected — on a mounted drive it can — but because on a shared drive the window where it sits in the wrong folder is the risk. See the hold rules in the agent.