Mostly efficient — compact tables, short rules, and tight command blocks instead of prose explaining Azure concepts. But the "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" blockquote is ceremonial filler and the Triggers section largely duplicates the WHEN clause already in the description, so it could be tightened. Not 3 because of that padding; not 1 because it does not explain concepts Claude already knows.

Provides copy-paste-ready executable commands — "az resource show --ids RESOURCE_ID", "az monitor activity-log list -g RG --max-events 20", "az containerapp logs show --name APP -g RG --follow", an App Insights KQL query — plus parameterized MCP invocation snippets. This matches fully executable, specific examples rather than pseudocode.

A clear numbered Quick Diagnosis Flow (identify symptoms, check resource health, review logs, analyze metrics, investigate changes) exists, but there are no explicit validation checkpoints or error-recovery feedback loops for operations that can be destructive/batch in nature. This matches "steps listed but validation gaps"; not 3 due to missing checkpoints, not 1 because the sequence is clear.

Good one-level-deep overview pointing to references/ files (container-apps, app-service, functions, kql-queries, azure-resource-graph) that all exist, with a service table and References section signaling navigation. However troubleshooting/aks/aks-troubleshooting.md and troubleshooting/messaging/README.md are referenced in the body but are missing from the bundle — dangling links that break navigation, preventing a 3.

Lists multiple concrete diagnostic actions and tools — "Debug Azure production issues... using AppLens, Azure Monitor, resource health, and safe triage" — matching the anchor for enumerating several specific concrete actions. It is above 2 because it goes well beyond naming a domain plus a few actions.

Explicitly answers both what ("Debug Azure production issues... using AppLens, Azure Monitor, resource health, and safe triage") and when via an explicit "WHEN:" trigger clause with concrete scenarios. An equivalent explicit trigger clause is present, so the missing-Use-when cap does not apply.

Natural trigger phrases a user/ops engineer would say are present in abundance: "troubleshoot app service", "app service high CPU", "troubleshoot AKS", "kubectl cannot connect", "pod pending", "crashloop", "image pull failures", "cold start issues", "AMQP connection failure", "message lock lost". Voice is imperative/third person ("Debug", "troubleshoot") with no first/second person, so no specificity penalty applies.

Anchored to Azure diagnostics (not generic), but its scope spans App Service, Container Apps, Functions, AKS, Event Hubs, and Service Bus, creating real overlap with dedicated service-specific skills. This matches "somewhat specific but could still overlap with similar skills"; it is not a tight distinct niche (3) yet not generic (1).