executive-digest

# Daily Executive Digest ## Config — read before starting Read `../config/user.json` (resolves to `~/executive-assistant-skills/config/user.json`). Extract and use throughout: - `primary_email`, `work_email` — both Gmail accounts to check - `whatsapp` — for delivery - `workspace` — absolute path to OpenClaw workspace Do not proceed until you have these values. ## Debug Logging (MANDATORY) Read `../config/DEBUG_LOGGING.md` for the full convention. Use `python3 {user.workspace}/scripts/skill_log.py exec-digest <level> "<message>" ['<details>']` at every key step. Log BEFORE and AFTER every external call (gog, mcporter, todoist-cli). On any error, log the full command and stderr before continuing. ## Steps ### 1. Read rules and state - Read `{user.workspace}/style/DIGEST_RULES.md` for format and rules - Read state files: - `{user.workspace}/state/scheduling-threads.json` — stalled threads (>3 days since proposed) - `{user.workspace}/state/decisions-memory.json` — context on people/companies - `{user.workspace}/state/digest-state.json` — avoid repeating items Schema: `{"lastRun": "ISO date", "surfacedItems": [{"id": "<thread_id|task_id>", "type": "intro|followup|draft|task|calendar", "surfacedAt": "ISO date"}]}`. Use consistent IDs: Gmail thread IDs for email items, Todoist task IDs for tasks, calendar event IDs for calendar items. Do NOT use semantic strings like "calendar:golf-mar5" — always use the actual service ID. An item is "repeated" if its ID appeared in the ...