# Pp Google Calendar > The multi-account Google Calendar layer for agents that must never surprise a human. Trigger phrases: `am I double-booked`, `check my calendars for conflicts`, `find me an open slot`, `what changed on my calendar`, `merge my google calendars`, `use google-calendar`, `run google-calendar-pp-cli`. - Skill: `mvanhorn-printing-press-libra/pp-google-calendar` (Agent Skill) - Install (CLI): `npx skillmds add mvanhorn-printing-press-libra/pp-google-calendar` - Raw SKILL.md: https://api.skillmd.com/api/skills/mvanhorn-printing-press-libra/pp-google-calendar/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - License: Apache-2.0 - Author: mvanhorn (https://skillmd.com/u/mvanhorn-printing-press-libra) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/mvanhorn-printing-press-libra/pp-google-calendar --- # Google Calendar — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `google-calendar-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install google-calendar --cli-only ``` 2. Verify: `google-calendar-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.5 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/productivity/google-calendar/cmd/google-calendar-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. Role-scoped OAuth profiles (a read-only account literally cannot write, by token), a conflicts engine whose all-clear carries coverage evidence, and mutations that are idempotent, etag-guarded, undo-bearing, and structurally incapable of emailing attendees. Built as the calendar substrate for an always-on personal-assistant agent; useful to anyone juggling multiple Google accounts from scripts. ## When to Use This CLI Reach for this CLI whenever schedule truth spans more than one Google account: conflict sweeps, availability questions, agenda merges, and gated calendar writes performed on a human's behalf. It is deliberately stateless — every answer is a live read with freshness evidence, so it suits agents whose answers must be citable. ## When NOT to Use This CLI Do not trigger this skill for: - **Gmail / email** — this CLI touches only the Calendar API; it cannot read or send mail. - **Google Tasks or Reminders** — not part of the Calendar events surface here. - **Calendar sharing / ACL changes** — granting or revoking access is out of scope by design; do it in the Calendar UI. `manifest check` only *reports* permission drift. - **Natural-language date parsing** ("next Tuesday-ish", quickAdd) — the caller resolves language to dates; this CLI takes explicit `YYYY-MM-DD`/RFC3339 (plus literal `today` and `+Nd` on window flags). - **Mutating attendee-bearing events or emailing invitees** — structurally refused: `sendUpdates=none` is forced on every mutation and events with attendees are never written by this tool. - **Availability of people outside the configured accounts** — verdicts cover only calendars in the approved calendars.yaml manifest. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Verdict contracts - **`conflicts`** — One command answers 'am I double-booked?' across every account, and refuses to give a confident all-clear over partial or stale data. _Reach for this whenever asserting schedule truth to a human — its downgrade semantics make the answer citable._ ```bash google-calendar-pp-cli conflicts --from 2026-08-18 --to 2026-08-25 --agent ``` - **`slots`** — Ranked open windows of a requested duration across all accounts, computed from live freebusy under the same busy semantics as conflicts. _Use when proposing meeting times — 'open' carries coverage evidence, not guesswork._ ```bash google-calendar-pp-cli slots --duration 90m --from 2026-08-18 --to 2026-08-22 --agent ``` ### Safe writes - **`events update`** — Writes take an etag precondition and return the pre-image plus a structured inverse operation, so every change is cleanly reversible and race-safe. _Use for any mutation an agent must be able to echo-with-undo to its principal._ ```bash google-calendar-pp-cli events update primary evt123 --account ads --start 2026-08-19T15:00:00-06:00 --if-etag "abc" --json ``` ### Governance and drift - **`changes`** — Everything that moved, appeared, or was cancelled across all accounts since a caller-held watermark — deletions included. _Run between full sweeps to catch mid-day schedule movement cheaply._ ```bash google-calendar-pp-cli changes --since 2026-08-17T07:00:00Z --agent ``` - **`manifest check`** — Diffs live calendar reality across all accounts against the approved calendars.yaml — new, missing, or permission-drifted calendars become findings. _Schedule this as hygiene; run it before trusting any multi-account verdict after account changes._ ```bash google-calendar-pp-cli manifest check --json ``` - **`events exceptions`** — Instances of recurring events that moved or were cancelled in a window — the routine-deviation surprises, isolated. _Use in look-ahead sweeps: deviations from routine are the highest-yield surprise class._ ```bash google-calendar-pp-cli events exceptions --from 2026-08-18 --to 2026-08-25 --agent ``` ## Command Reference **accounts** — gauth profiles - `google-calendar-pp-cli accounts` — List gauth profiles and each token's status (roles decide OAuth scopes). - `google-calendar-pp-cli accounts auth --account ` (or `--all`) — Run the browser OAuth flow for one profile (or every profile), requesting only the profile role's scopes. **agenda / calendars** — merged reads - `google-calendar-pp-cli agenda --from --to ` — Merged agenda across every manifest calendar, sorted by start, with per-source freshness and a coverage block. - `google-calendar-pp-cli calendars` — Merged calendar list across all accounts (account, summary, access role, id). - `google-calendar-pp-cli calendars --account ` — Metadata for one calendar. **calendars events** — per-calendar event CRUD (every mutation passes the safety barrier: `sendUpdates=none` forced, attendee-bearing events refused, etag preconditions) - `google-calendar-pp-cli calendars events list ` — Events on one calendar (`--q`, `--time-min`, `--time-max`, `--single-events`, `--show-deleted`, ...). - `google-calendar-pp-cli calendars events get ` — One event. - `google-calendar-pp-cli calendars events instances ` — Instances of a recurring event. - `google-calendar-pp-cli calendars events insert ` (alias `create`) — Create an event. - `google-calendar-pp-cli calendars events update|patch ` — Full/partial update (prefer the top-level `events update` for the undo-bearing contract). - `google-calendar-pp-cli calendars events delete ` — Delete an event. - `google-calendar-pp-cli calendars events move --destination ` — Move an event to another calendar. **free-busy** — raw passthrough - `google-calendar-pp-cli free-busy --items --time-min --time-max ` — Free/busy for a set of calendars on one account. Prefer `slots`/`conflicts` for cross-account availability verdicts. **doctor** - `google-calendar-pp-cli doctor` — Health check (`--fail-on warn` for automation). ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash google-calendar-pp-cli which "" ``` `which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query. ## Recipes ### Morning conflict sweep ```bash google-calendar-pp-cli conflicts --from today --to +7d --agent ``` The daily verdict: overlaps, mirrors flagged separately, and an explicit coverage line. ### Narrow a verbose agenda for context-poor consumers ```bash google-calendar-pp-cli agenda --from today --to +2d --agent --select events.summary,events.start,events.account ``` Dotted-path narrowing keeps multi-account agenda payloads small enough for tight agent contexts. ### Find 90 minutes this week ```bash google-calendar-pp-cli slots --duration 90m --from today --to +5d --between 09:00-17:00 --agent ``` Ranked open windows under the same busy semantics as conflicts — no false frees. ### What moved since 7am ```bash google-calendar-pp-cli changes --since 2026-08-17T07:00:00Z --agent ``` Stateless mid-day sweep; cancellations included. ### Reversible reschedule ```bash google-calendar-pp-cli events update primary evt123 --account ads --start 2026-08-19T15:00:00-06:00 --if-etag "etag-from-read" --json ``` Fails cleanly if the event changed since you read it; response carries the pre-image and inverse op. ## Auth Setup Auth is per-profile installed-app OAuth: you supply a client.json from your own Google Cloud project, then run auth --account once per account. Each profile declares a role — readonly profiles request calendar.readonly only, so write scopes never exist on that token. Tokens live in the configured token dir, never in the repo. Run `google-calendar-pp-cli doctor` to verify setup. ## Agent Mode Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color --yes`. - **Pipeable** — JSON on stdout, errors on stderr - **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs: ```bash google-calendar-pp-cli calendars primary --account personal --agent --select id,summary,accessRole ``` - **Previewable** — `--dry-run` shows the request without sending - **Offline-friendly** — sync/search commands can use the local SQLite store when available - **Non-interactive** — never prompts, every input is a flag - **Explicit retries** — use `--idempotent` only when an already-existing create should count as success, and use `--ignore-missing` only when a missing delete target should count as success ### Response envelope Commands that read from the local store or the API wrap output in a provenance envelope: ```json { "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."}, "results": } ``` Parse `.results` for data and `.meta.source` to know whether it's live or local. A human-readable `N results (live)` summary is printed to stderr only when stdout is a terminal AND no machine-format flag (`--json`, `--csv`, `--compact`, `--quiet`, `--plain`, `--select`) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout. ## Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: - Use `--home ` for one invocation, or set `GOOGLE_CALENDAR_HOME=` to relocate all four path kinds under one root. - Use per-kind env vars only when a specific kind must diverge: `GOOGLE_CALENDAR_CONFIG_DIR`, `GOOGLE_CALENDAR_DATA_DIR`, `GOOGLE_CALENDAR_STATE_DIR`, `GOOGLE_CALENDAR_CACHE_DIR`. - Resolution order is per-kind env var, `--home`, `GOOGLE_CALENDAR_HOME`, XDG (`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME`), then platform defaults. - `config` contains settings like `config.toml` and profiles. `data` contains `credentials.toml`, `data.db`, cookies, and auth sidecars. `state` contains persisted queries, jobs, and `teach.log`. `cache` contains regenerable HTTP/cache files. - Stored secrets live in `credentials.toml` under the data dir. Existing legacy `config.toml` secrets are read for compatibility and leave `config.toml` on the first auth write. - Run `google-calendar-pp-cli doctor --fail-on warn` to surface path and credential-location warnings. `agent-context` exposes a schema v4 `paths` block for agents that need the resolved dirs. - For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags: ```json { "mcpServers": { "google-calendar": { "command": "google-calendar-pp-mcp", "env": { "GOOGLE_CALENDAR_HOME": "/srv/google-calendar" } } } } ``` Fleet precedence: an inherited per-kind env var overrides an explicit `--home` for that kind. Use `GOOGLE_CALENDAR_HOME` or per-kind vars as durable fleet levers, and use `--home` only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing `GOOGLE_CALENDAR_HOME`, or `doctor` will not find credentials left under the former root. ## Automatic learning This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a `flag_alias` candidate, and a `teach` on a query family without a playbook auto-synthesizes a `playbook_candidate` from the session's journal. Your job is judgment only: `recall` first, act on surfaced candidates, `teach` the final answer, `playbook amend` when you observe a correction. You never record failures by hand. ### Step 1: `recall` before any discovery Before list/search/drill commands on a new user question, run: ```bash google-calendar-pp-cli recall "" --agent ``` The response envelope: ```json { "query": "...", "normalized": "", "query_entities": ["..."], "found": true | false, "match_score": 0.0, "results": [ { "resource_id": "...", "resource_type": "...", "venue": "...", "confidence": 2, "entity_match": "exact|partial|unknown", "source": "taught|preseed|pattern", "warnings": ["..."] } ], "mismatches": [ /* only when --debug-mismatches */ ], "warnings": [ /* top-level */ ], "candidates": [ { "id": 12, "class": "flag_alias | playbook_candidate", "summary": "...", "sightings": 3, "last_seen": "...", "rationale": "...", "next_action": ["", "google-calendar-pp-cli learnings confirm 12"] } ], "playbook": { "query_family": "...", "playbook": { "steps": [ { "cmd": "", "purpose": "..." } ], "entity_slots": ["$ENTITY"], "expected_tool_calls": 3 }, "slots_resolved": { "$ENTITY": { "token": "", "canonical": "" } }, "notes": "" }, "notes": "" } ``` Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and `learnings list` and `learnings candidates` are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught. ### Step 2: decision tree Read `candidates`, `playbook`, `notes`, `results[0]`, and warnings in that order: ``` if Candidates present (warnings include "candidates_present"): -> candidates are try-then-confirm, never facts. Follow each candidate's two-step next_action verbatim: run the trial command first, then run `learnings confirm ` only after the trial verified the behavior. Reject a wrong candidate with `learnings reject `. -> NEVER re-teach something recall surfaced as a candidate; confirm or reject that candidate instead of teaching a duplicate. -> candidates ride alongside playbooks and resource hits, not instead of them; continue with the branches below after acting on them. if Playbook present: -> READ Playbook.notes verbatim FIRST (workarounds + gotchas the CLI surface doesn't expose) -> replay Playbook.steps in order, substituting Playbook.slots_resolved entries for the entity slot tokens. If a step's slot is unresolved, fall back to discovery for that step only. -> the Playbook's expected_tool_calls is a budget; if you find yourself running materially more, record the divergence via `google-calendar-pp-cli playbook amend` at end-of-session. elif Notes present (no Playbook): -> read Notes verbatim before any discovery step; they carry known gotchas for this query family even when no structured choreography exists yet. elif Found AND Results[0].EntityMatch == "exact" AND Results[0].Confidence >= 2: -> skip discovery; fetch live data for Results[*].ResourceID in parallel elif Found AND Results[0].EntityMatch == "partial": -> candidate hint, NOT a hit; read the resource title to validate before trusting elif (any row in Mismatches[] when --debug-mismatches was passed): -> treat as cold start; the stored learning is for a different entity (different canonical resolved from query_entities) else: // Found == false, no playbook, no notes -> cold start; run discovery normally; teach the answer afterward (Step 4). If the family has no playbook yet, that teach auto-synthesizes a playbook candidate from this session's journal - you do not need to record one by hand. ``` Playbook and Notes are orthogonal to the per-resource path. A recall response can carry both a Playbook AND a `Results[]` hit - use both: the Playbook tells you which choreography to run; the resource hits short-circuit specific steps. Default to skipping `mismatches`; pass `--debug-mismatches` only when investigating cold-start surprises. Candidate judgment details: `learnings confirm ` prints the candidate's full payload before materializing it - check that the printed payload matches the behavior you verified. `learnings reject ` tombstones the derivation signature so the same candidate does not resurface. The envelope carries only the few candidates worth acting on now; `google-calendar-pp-cli learnings candidates` lists the full open set. Graceful degradation: if `learnings confirm` is an unknown command, you are driving an older binary - ignore the candidates guidance and follow the rest of the protocol. ### Step 3: always read `warnings` - `low_confidence`: row exists at `confidence<2`. Treat as a hint, not a skip-discovery hit. - `resource_not_in_store`: the local store doesn't have the resource the learning points at. The match validator couldn't classify entities — direct-fetch and re-evaluate. - `cross_alias_match` (per-result): the row was taught under a different alias and matched the live query's canonical via `entity_lookups` (e.g., a "USA" teach satisfying a "United States" recall). Trust the resource_id. - `similar_shape_different_entity:` (top-level): a structurally matching row exists but its canonical entity differs from the live query's. Treated as cold start; the warning carries the conflicting canonical as a hint, but the row is NOT promoted into Results. - `ambiguous_alias` (top-level): a single query entity resolved to multiple canonicals (e.g., "Cards" → Arizona Cardinals + St. Louis Cardinals). Surface the ambiguity from context before committing to a resource. - `candidates_present` (top-level): the envelope carries a `candidates` section. Handle it via the candidates branch in Step 2 before anything else. - `lookup_refresh_available` (top-level): an entity in the query has no lookup row yet, but synced data could provide one. Run `google-calendar-pp-cli sync` to refresh entity lookups. - Top-level `no_learnings_for_query_family`: the table had no rows above the Jaccard floor. Pure cold start. ### Step 4: `teach &` after finalizing your response - always Teaching is unconditional. After resolving a query the store could not answer, background-teach the final resource mapping - no call-count threshold, no judging whether it was "worth" learning. The teach is the anchor of the loop: it triggers playbook synthesis for a family without a playbook, and same-referent phrasings fold into one family so near-duplicate teaches do not fragment the store. Fire it after assembling your user-facing response but BEFORE emitting it, with a shell `&` so the call returns immediately: ```bash google-calendar-pp-cli teach --query "" --resource-type --resource --resource # (append shell `&` to background it) ``` Silent on success. Errors only land in `teach.log` under the resolved state dir. Teach the **most specific** resource - if the user asked a broad question and you walked through parent records to find the specific answer, teach the leaf id, not the parent. The CLI uses seeded `entity_lookups` for cross-alias resolution at recall time, so a teach under one alias (e.g., "Niners") satisfies future queries under another alias (e.g., "49ers", "San Francisco") automatically. PII rule: teach the structural question with identifiers stripped - never include names, emails, phone numbers, account ids, or other personal identifiers in taught queries or notes. The CLI scans teach queries for obvious email/phone shapes and warns, but does not block; strip before teaching rather than relying on the warning. ### Step 5: playbooks - optional flags, automatic synthesis You do not need to decide whether a session "deserves" a playbook: a teach on a family without one auto-synthesizes a `playbook_candidate` from the session's journal, and the next session judges it via confirm/reject. Attach explicit playbook flags only when you already hold choreography worth recording verbatim - workarounds the CLI didn't surface (silently-dropped flags, undocumented params, pagination tricks, payload gotchas). Prefer the **integrated one-call form** - record the resource learning and the playbook in the same `teach` invocation: ```bash # Common case: record both the resource learning AND the playbook in one call. google-calendar-pp-cli teach \ --query "" \ --resource \ --playbook-file ~/playbooks/.json \ --playbook-notes-file ~/playbooks/-notes.md # (append shell `&` to background it) # Alternate: playbook-only (no resource to record alongside). google-calendar-pp-cli teach-playbook \ --query "" \ --playbook-file ~/playbooks/.json \ --notes-file ~/playbooks/-notes.md ``` Playbook files are JSON with `steps`, `entity_slots`, `expected_tool_calls`. Notes files are markdown carrying the gotchas verbatim. File-free callers (MCP-only agents) pass the same content inline: `--playbook-json` and `--playbook-notes` on the integrated `teach` form, `--playbook-json` and `--notes` on `teach-playbook`. On the integrated `teach` form, the playbook flags are optional - omit them entirely for a resource-only teach. On the standalone `teach-playbook` form, at least one of the playbook and notes flags must be set; both empty is rejected. Playbooks are keyed on the structural query family (entities stripped) so a recipe taught from one entity-shaped query applies to every other query of the same shape, with `slots_resolved` binding the live query's canonical at recall time. When you DO find a playbook on a future recall, treat it as ground truth: replay the steps with `slots_resolved` substitutions, skip the discovery that the choreography already documents, and read `notes` before any step. ### Step 6: `playbook amend &` when your debug response identifies a correction If your debug-protocol response identifies a concrete correction the notes or playbook should know — a workaround, an undocumented endpoint shape, a stale field name, observed schema drift, an empty-payload fallback — fire `playbook amend` BEFORE emitting your user-facing response. Same fire-and-forget posture as `teach`. ```bash google-calendar-pp-cli playbook amend \ --query "" \ --add-note "" # (append shell `&` to background it) ``` What counts as worth amending: a behavior you OBSERVED this session that future-you would benefit from knowing. Examples worth amending: - A workaround for a CLI surface that silently drops or misorders a flag. - An undocumented endpoint shape (response wrapped in `{meta, results}`, payload nested two levels deeper than the docs claim). - Observed schema drift (a field renamed, an index that shifted between seasons, a category label that the API now returns lower-cased). What does NOT belong in notes: - The year-specific or entity-specific answer to the user's question. That's the response, not a learning. - Per-team / per-athlete / per-row data the playbook already retrieves at runtime. - Statements that paraphrase what the existing notes already say. The amend command appends to the family's existing notes with a timestamped marker (`[amend YYYY-MM-DDTHH:MMZ]: `). Multiple amends accumulate; the audit trail is visible. If no playbook exists yet for the family, amend creates a notes-only one (so cold-start corrections still land). #### PII discipline for amend notes `playbook amend` notes are designed to potentially flow upstream as shared knowledge in future versions of the Printing Press. Keep them clean of user-identifying content so the upstream-contribution path stays open without retroactive scrubbing: - **Do NOT embed** paths to user filesystems, personal API keys or tokens, user email addresses, user GitHub handles, or specific query histories tied to a single user. - **Acceptable**: endpoint shapes, undocumented field names, API gotchas, observed schema drift, workarounds for CLI surfaces, generalizable pagination or retry tactics. If a correction is only meaningful with user-specific context, it belongs in a personal note, not in the playbook amend. ### Measuring the loop `google-calendar-pp-cli learnings stats` reports recall hit rate, teach-to-reuse, playbook resolution rate, and candidate confirm/reject counts from the local `learn_events` table. Rates are null until they have a denominator; everything stays on this machine. Use it to check whether the loop is earning its keep for this CLI. ### Disabling learning - `--no-learn` on a single command short-circuits both `recall` and the `teach` write path. Use for deterministic agent flows or tests that must not be affected by accumulated learnings. - `GOOGLE_CALENDAR_NO_LEARN=true` in the environment globally disables the pipeline. ## Agent Feedback When you (or the agent) notice something off about this CLI, record it: ``` google-calendar-pp-cli feedback "the --since flag is inclusive but docs say exclusive" google-calendar-pp-cli feedback --stdin < notes.txt google-calendar-pp-cli feedback list --json --limit 10 ``` Entries are stored locally as `feedback.jsonl` under the resolved data dir. They are never POSTed unless `GOOGLE_CALENDAR_FEEDBACK_ENDPOINT` is set AND either `--send` is passed or `GOOGLE_CALENDAR_FEEDBACK_AUTO_SEND=true`. Default behavior is local-only. Write what *surprised* you, not a bug report. Short, specific, one line: that is the part that compounds. ## Output Delivery Every command accepts `--deliver `. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported: | Sink | Effect | |------|--------| | `stdout` | Default; write to stdout only | | `file:` | Atomically write output to `` (tmp + rename) | | `webhook:` | POST the output body to the URL (`application/json` or `application/x-ndjson` when `--compact`) | Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr. ## Named Profiles A profile is a saved set of flag values, reused across invocations. Use it when a scheduled or recurring agent reuses the same saved flags while providing different input each run. ``` google-calendar-pp-cli profile save briefing --json google-calendar-pp-cli --profile briefing agenda --from today --to +2d google-calendar-pp-cli profile list --json google-calendar-pp-cli profile show briefing google-calendar-pp-cli profile delete briefing --yes ``` Explicit flags always win over profile values; profile values win over defaults. `agent-context` lists all available profiles under `available_profiles` so introspecting agents discover them at runtime. ## Exit Codes | Code | Meaning | |------|---------| | 0 | Success | | 2 | Usage error (wrong arguments) | | 3 | Resource not found | | 4 | Authentication required | | 5 | API error (upstream issue) | | 7 | Rate limited (wait and retry) | | 10 | Config error | **Verdict commands override 3 and 4 with typed meanings** — do not read them as "not found"/"auth required" there: | Command | Typed exits | |---------|-------------| | `conflicts` | 0 = no conflicts, complete coverage; 3 = conflicts found; 4 = no conflicts but coverage incomplete (degraded all-clear) | | `manifest check` | 0 = clean; 3 = findings (missing/role-drifted entries); 4 = no findings but an account unreadable | | `slots` / `changes` / `events exceptions` / `agenda` | 0 = complete coverage; 4 = one or more sources unreadable | ## Argument Parsing Parse `$ARGUMENTS`: 1. **Empty, `help`, or `--help`** → show `google-calendar-pp-cli --help` output 2. **Starts with `install`** → ends with `mcp` → MCP installation; otherwise → see Prerequisites above 3. **Anything else** → Direct Use (execute as CLI command with `--agent`) ## MCP Server Installation Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it: ```bash claude mcp add google-calendar-pp-mcp -- google-calendar-pp-mcp ``` Verify: `claude mcp list` ## Direct Use 1. Check if installed: `which google-calendar-pp-cli` If not found, offer to install (see Prerequisites at the top of this skill). 2. Match the user query to the best command from the Unique Capabilities and Command Reference above. 3. Execute with the `--agent` flag: ```bash google-calendar-pp-cli [subcommand] [args] --agent ``` 4. If ambiguous, drill into subcommand help: `google-calendar-pp-cli --help`.