setup

Files (1)

• SKILL.md

SKILL.md (first lines)

Run the environment check (migrates any legacy session into the stable data dir, then reports):
```bash
cd "${CLAUDE_PLUGIN_ROOT}" && npx tsx --env-file-if-exists=.env scripts/doctor.ts
```

The script can only check what a local process can see. After it runs, also do the two checks it
cannot, then guide the user:

1. Loom session (REQUIRED): if missing, run `/loom-daddy:loom-auth`. This is the only hard
   requirement for analyzing recordings.
2. Notion MCP (REQUIRED for publishing, script cannot check): confirm a Notion MCP is connected
   and callable in this session (interactive uses the `notion-search`/`notion-create-pages`
   tools). If none is connected, tell the user to connect their Notion integration; publishing
   needs it. No `NOTION_TOKEN` is required.
3. Notion destination: if none is cached yet, tell the user they will name a target database on
   their first `/loom-daddy:publish` (e.g. "publish to my Meeting Notes database"); it is then
   remembered.
4. Drive (OPTIONAL): only needed to also upload a transcript + markdown copy. If unset, Drive is
   skipped and Notion publishing still works. To enable, set DRIVE_FOLDER_ID +
   GOOGLE_APPLICATION_CREDENTIALS in `${CLAUDE_PLUGIN_ROOT}/.env`.

No LLM API key is needed (analysis runs on the Claude subscription). When the session is present,
suggest `/loom-daddy:list` to see recent recordings.

From fontezbrooks/loomDaddy, MIT.

More from fontezbrooks/loomDaddy