worklog

Capture one work-log entry into **three** targets. Distinguish two failure kinds: - **Misconfiguration is loud.** If a target's env var is unset, that is a setup error — **report it prominently** so it gets fixed, don't skip it quietly. - **Transient failure is best-effort.** If a *configured* target is momentarily unreachable (server down, Notion MCP disconnected), never block the caller — note it and move on. The local mirror is the source of truth. An end-of-day cloud routine summarizes the Notion raw entries into narrative sections, so this skill only appends; it never summarizes. ## Compose the entry Determine what to log: - If the caller (e.g. `/handoff`) or the user supplied text or a summary, use it. - Otherwise, summarize the current thread of work yourself: what got done, key decisions, and the top next action. Keep it tight: `summary` is 3-5 short bullets; `next` is the top 1-3 next actions. **Redact secrets** — never put tokens, keys, passwords, or PII in the entry. ## Configuration Two targets are configured via env vars (set in the `env` block of `~/.claude/settings.json`, alongside the `ZOTERO_*` keys) — no personal infrastructure is hardcoded in this skill. **If a var is unset, surface it loudly as a setup error** (`worklog: <VAR> unset — this target is not configured; set it in ~/.claude/settings.json`) so the gap gets fixed, rather than silently dropping the target: - `WORKLOG_SSH_TARGET` — `user@host` for the server cache (e.g. a Tailscale h...