Conciseness

"Requires: existing AKS cluster, `az login`, `kubectl` configured" and the bare "DS001–DS013 failures" trigger phrase assume Claude's competence with zero concept explanations; all ~26 lines are navigation or scoping. Matches the lean-and-efficient anchor. Not 4 because there is no over-explanation to trim anywhere in the body.

Actionability

Guidance is pointer-shaped — "Follow `phases/quick-deploy.md`", "Load `knowledge-packs/frameworks/<framework>.md` per detected framework", "`templates/` (dockerfiles/, k8s/, github-actions/, mermaid/)" — with prerequisites (`az login`, `kubectl`) but no executable command or step for the core deploy task in the body itself. Not 4 because nothing in the body is copy-paste executable; not 2 because the pointers and prerequisites are specific and correctly targeted.

Workflow Clarity

A rough sequence exists — prerequisites, "Follow `phases/quick-deploy.md`", "On failure: `references/rollback.md`" — but validation checkpoints are only implicit (verification is mentioned in the description, never as a body step) and the actual step sequence is delegated to a file absent from the bundle. Matches the steps-listed-but-checkpoints-missing anchor. Not 4 because no explicit validate/verify step appears in the body.

Progressive Disclosure

The References section is well signaled with one-line descriptions ("[safeguards.md](./references/safeguards.md) — DS001-DS013 checklist"), but the primary workflow pointer `phases/quick-deploy.md` plus `knowledge-packs/frameworks/` and `templates/` do not exist in the provided bundle, so the skill's main navigation path dangles. Not 4 because missing referenced paths are a navigation failure beyond "minor organization gaps"; not 2 because the references/ files that do exist are clearly organized one level deep.

Specificity

"Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification" lists four concrete actions covering the full detect→generate→validate→deploy→verify lifecycle, matching the comprehensive-coverage anchor. Not 4 because there are no coverage gaps across the deployment workflow.

Completeness

The 'what' is explicit ("Detects the framework, generates a Dockerfile and Kubernetes manifests, validates... and deploys with verification") and the 'when' is explicit via the WHEN: clause with concrete trigger phrases, plus a DO NOT USE FOR boundary — the anchor-5 pattern. Not 4 because both what and when are fully explicit, not merely present.

Trigger Term Quality

Natural user phrasings like "my AKS deployment is failing safeguard checks", "I have a Django/Express/Spring Boot app to run on AKS", and "set up CI/CD for AKS" appear alongside synonyms (AKS, K8s, Kubernetes, Azure) and concrete framework names, matching the comprehensive synonym coverage anchor. Not 4 because common variations users would actually say are already well represented.

Distinctiveness Conflict Risk

"DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic..., or deploying to non-AKS targets like Web Apps, Container Apps, or Functions" explicitly disambiguates sibling skills, and the niche (deploy apps to an already-running AKS cluster) has distinct triggers. Not 4 because conflict risk with adjacent skills is actively resolved by named exclusions.