Conciseness

Lean and dense with operational knowledge Claude would not already know ('Record the raw request bodies, not parsed ones: alertUniqueIds: {} and {"value": []} parse alike but are different requests', 'Plan the applied config again after each refresh'). Every token earns its place with no padding or generic explanation.

Actionability

Mostly executable: concrete commands ('tfgen check --overrides', 'tfgen generate --resource <Name> --out <dir>'), real file paths ('internal/provider/global_router_baseline_*_test.go', 'behavior-overrides.yaml'), and named test procedures. Not 5 because a couple of steps lack executable detail — no example line of an overrides file, and 'Record real answers with a recorder that stays outside the repo' names no tool or command.

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints guarding the destructive step (delete handwritten code): 'The golden diff must show only wording of messages', 'The diff must be empty', 'Do not keep a bug with an override line', and 'Keep the hand test until the generated one has passed on a tenant' — feedback loops and error-recovery gates are all present.

Progressive Disclosure

A ~20-line skill with well-organized sections (Trigger, Recipe, Why) and no bundle files; all detail is appropriately inline for this length, so the simple-skill exception applies and organization is clean.

Specificity

Names the domain ('tools/iac-codegen existing-resource mode') and two concrete actions ('Record a baseline first, then compare'), but does not enumerate the skill's fuller action set (overrides, generation, acceptance tests), matching the 'domain and 1-2 concrete actions' anchor rather than the 'several specific actions' level.

Completeness

Both parts are present: an explicit 'Use when a handwritten resource that users already have becomes generated code' trigger (plus the exclusion 'Do NOT use for a new resource') and a what ('Record a baseline first, then compare'). The when is concrete, but the what is thin — only two actions — so it falls short of the anchor-5 'clearly and explicitly answers both with concrete trigger phrases' for the what side.

Trigger Term Quality

Natural phrases users would actually say are present — 'handwritten resource', 'generated code', 'existing-resource', 'new resource' — giving good keyword coverage. Not 5 because common synonyms like 'migrate', 'convert', 'switch', or 'Terraform provider' are missing; not 3 because the terms directly mirror natural user phrasing rather than only loosely relevant keywords.

Distinctiveness Conflict Risk

Highly niche ('tools/iac-codegen existing-resource mode') with a clear distinct trigger and an explicit negative trigger ('Do NOT use for a new resource') that separates it from the nearest competing use case, giving minimal conflict risk.