azure-diagnostics

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, service bus dead letter.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.github/plugins/azure-skills/skills/azure-diagnostics/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A reasonably actionable and structured diagnostic skill body with concrete CLI commands and a clear diagnosis flow. It is held back by duplicated content, no explicit validation checkpoints, and three dangling troubleshooting reference paths that do not exist in the bundle.

Suggestions

Remove the duplicate 'az resource show' / 'az monitor activity-log list' command block (present in both Quick Reference and Check Azure Resource Health) and trim the 'AUTHORITATIVE GUIDANCE' banner to reduce token cost.

Add explicit validation/feedback steps to the Quick Diagnosis Flow (e.g., 'If resource health is degraded, stop and surface the health event before log analysis') rather than a flat checklist.

Create the missing troubleshooting/aks, troubleshooting/compute, and troubleshooting/messaging files referenced in the Routing section, or repoint those links to existing references/ paths so no navigation links dangle.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with a tight Rules section and useful command snippets, but the Triggers section repeats the description's triggers, 'az resource show'/'az monitor activity-log list' are duplicated across two sections, and the 'AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE' banner adds padding without information.	3 / 5
Actionability	Provides concrete copy-paste CLI commands (az containerapp logs show, az monitor app-insights query) and MCP tool parameter blocks; minor gaps remain since the MCP blocks use a pseudo-format rather than real tool-call syntax.	4 / 5
Workflow Clarity	The Quick Diagnosis Flow gives a clear 5-step sequence and the Rules supply routing guidance, but there are no explicit validation checkpoints or feedback (validate->fix->retry) loops, and several routing steps point elsewhere without verifying outcomes.	3 / 5
Progressive Disclosure	The body is a well-structured overview with a service table and clear reference links, but three routing links (troubleshooting/aks/aks-troubleshooting.md, troubleshooting/compute/vm-troubleshooting.md, troubleshooting/messaging/README.md) point to files that do not exist in the bundle, breaking navigation.	3 / 5
	Total	13 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description that clearly states both capability and an extensive explicit WHEN trigger list in third person. Minor redundancy ('on Azure') and broad multi-service scope are the only weak points.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure production issues') and concrete actions/tools ('Debug', 'troubleshoot', 'AppLens', 'Azure Monitor', 'resource health', 'safe triage') with comprehensive scenario coverage, though the action verbs are somewhat repetitive across services rather than distinct concrete operations.	4 / 5
Completeness	Explicitly answers both what ('Debug Azure production issues ... using AppLens, Azure Monitor, resource health, and safe triage') and when (a 'WHEN:' clause listing concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Exhaustive natural-language triggers users would actually say ('app service high CPU', 'app service deployment failure', 'kubectl cannot connect', 'pod pending', 'crashloop', 'reset VM password', 'message lock lost', 'service bus dead letter') including synonyms and error-specific phrasings.	5 / 5
Distinctiveness Conflict Risk	Has a clear Azure-production-diagnostics niche with distinct service-specific triggers, but the breadth (App Service, Functions, AKS, VMs, Messaging) creates minor overlap risk with potential dedicated per-service skills.	4 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 8 missing, 13 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 5 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: microsoft/azure-skills
Path: .github/plugins/azure-skills/skills/azure-diagnostics/SKILL.md
Commit: 9d46511

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.