Conciseness

The body is ~35 lines with zero concept explanations or padding: a one-line purpose, a delegated pointer for shared rules, an executable safe-start block, a compact command table, and pointers to --help and the schema contract. Every token earns its place, matching anchor 5.

Actionability

The safe-start block is fully executable and copy-paste ready (auth check, schema fetch, a read-only search example), and the body directs to `gog contacts <command> --help` and `gog schema contacts <command> --json` for exact syntax. It stops short of anchor 5 because no example invocation exists for any write command (create/update/delete/batch), leaving the most common mutation cases without a concrete example.

Workflow Clarity

Despite destructive and batch operations being present, the required validation checkpoints exist ('--dry-run before supported writes', 'Confirm the exact account, object, and mutation before any write or delete', '--readonly', and an auth/schema check before any operation), so the batch/destructive cap at 3 does not apply. It remains at anchor 4 rather than 5 because there is no post-write verification step or error-recovery loop (what to do when a command fails).

Progressive Disclosure

The skill is under 50 lines, cleanly sectioned (Safe start, Commands), and correctly delegates bulk detail: shared auth/safety rules to the one-level-deep `../gog/SKILL.md` reference and per-command flag contracts to `gog schema contacts <command> --json` instead of inlining an API reference. Per the simple-skill guideline, this scores 5 with well-organized sections and no unnecessary external reference files.

Specificity

The description names the domain ("Google Contacts") but the only action word is the generic "operations" — no concrete verbs like create, search, update, or delete. This matches anchor 2 ('Names the domain but actions are minimal or generic') and falls short of anchor 3, which requires 1-2 concrete actions.

Completeness

There is no "Use when..." trigger clause at all, and the 'what' is itself vague ("operations" conveys no specific capability). This matches anchor 2 ('Has a vague what and no when') rather than anchor 3, whose example lists concrete capabilities even without a when-clause.

Trigger Term Quality

"Google Contacts" and "gog" are natural terms a user would say, but there are no variations or synonyms ("contacts", "address book", "People API"). Anchor 3 ('Some relevant keywords but missing common variations') is the closest fit; anchor 4 requires noticeably broader keyword coverage.

Distinctiveness Conflict Risk

"Google Contacts" plus the specific tool "gog" carves a clear, distinct niche with minimal conflict risk. It sits at anchor 4 rather than 5 only because the thin description provides few trigger phrases to distinguish it from sibling gog skills (e.g., Gmail contact management).