Conciseness

The body is lean with zero padding: a 3-command 'Safe start' block, flag guidance as terse bullets, a purpose-per-row command table, and a one-line discovery pointer ('Run gog calendar <command> --help... Do not guess command syntax.'). It assumes Claude's competence and never explains concepts Claude already knows, matching anchor 5.

Actionability

The 'Safe start' commands are concrete and copy-paste ready (e.g. 'gog --readonly --account user@example.com calendar events --today --json --wrap-untrusted'), and the mandated --help/schema discovery path is fully executable. Not 5 because no example of an actual write operation (e.g. a 'create' or 'update' invocation) is shown, leaving the most common cases covered only via discovery rather than example — anchor 4 (minor gaps).

Workflow Clarity

There is a clear sequenced start (auth check → schema contract → read-only events) with explicit pre-write checkpoints: '--dry-run before supported writes' and 'Confirm the exact account, object, and mutation before any write or delete.' Not 5 because destructive commands (delete, delete-calendar) lack a post-write verification step or error-recovery loop; the validation present is pre-write only, matching anchor 4 (most checkpoints, minor validation gaps).

Progressive Disclosure

Well-organized sections ('Safe start', 'Commands') with shared rules factored into a clearly signaled one-level-deep reference ('Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules.') and flag details delegated to on-demand --help/schema output instead of being inlined. No bundle files exist to nest, and the single external reference is purpose-labeled — anchor 5.

Specificity

"Google Calendar operations through gog" names the domain and tool but "operations" is generic — no concrete actions like create/update/delete events or free/busy checks are listed. This matches anchor 2 (domain named, actions minimal or generic); it is not 3 because no concrete action is enumerated, and not 1 because the domain and tool are explicitly named.

Completeness

The description provides only a domain-level "what" ("Google Calendar operations") with no "when" guidance at all — the "Use when..." clause is entirely missing. It sits between anchor 2 (vague what, no when) and anchor 3 (clear what, no when): the what is more informative than pure fluff but names no concrete operation, so per boundary guidance it scores the even value 2; the missing "Use when..." clause also caps it below 4.

Trigger Term Quality

"Google Calendar" is a natural phrase users would say, but "gog" is tool-specific jargon and common synonyms (events, meetings, appointments, schedule, invites) are absent. Matches anchor 3 (some relevant keywords, missing common variations); not 4 because keyword coverage is thin rather than merely missing a few terms.

Distinctiveness Conflict Risk

"Google Calendar" carves a clear, distinct niche with a specific tool, so overlap risk is minor — mainly with sibling gog module skills (e.g., Gmail, Drive). Not 5 because there are no explicit trigger phrases and "operations" is broad enough to brush against other calendar/scheduling skills.