Skills azure-diagnostics
📦

azure-diagnostics

Safe

Debug Azure Production Issues

This skill helps developers diagnose and troubleshoot production issues in Azure by providing structured debugging workflows, diagnostic commands, and KQL queries for Container Apps.

Supports: Claude Codex Code(CC)
📊 69 Adequate
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "azure-diagnostics". My Container App shows status 'Running' but returns 502 errors

Expected outcome:

  • Check the ingress targetPort configuration matches your app's listening port
  • Verify the health endpoint returns HTTP 200
  • Review container startup logs for errors
  • Ensure Dockerfile EXPOSE matches ingress configuration

Using "azure-diagnostics". Write a KQL query to find failed requests

Expected outcome:

  • AppRequests
  • | where Success == false
  • | where TimeGenerated > ago(1h)
  • | summarize count() by Name, ResultCode
  • | order by count_ desc

Security Audit

Safe
v1 • 2/20/2026

This skill contains only documentation with example Azure CLI commands and KQL queries. Static scanner flagged 70 instances of 'external_commands' but these are markdown code blocks showing example commands, not executable code. Network findings are documentation URLs. Env access findings reference standard Azure Container Apps environment variables. All high/critical findings are false positives - the skill is safe for publication.

4
Files scanned
393
Lines analyzed
5
findings
1
Total audits

Critical Issues (1)

False Positive: Dangerous Combination Heuristic
Scanner flagged 'Code execution + Network + Credential access' pattern. This is a documentation skill with no executable code. The 'external_commands' findings are Azure CLI examples in markdown code blocks. Network findings are documentation URLs. No credential access exists.

High Risk Issues (1)

False Positive: Weak Cryptographic Algorithm
Scanner flagged 'Weak cryptographic algorithm' in KQL query files. This is a false positive - the scanner misinterprets KQL keywords like 'where', 'state' as cryptographic terms. These are Kusto Query Language queries for log analysis.
Medium Risk Issues (3)
False Positive: External Commands in Documentation
Scanner flagged 70 instances of 'Ruby/shell backtick execution'. These are Azure CLI commands shown in markdown code blocks as documentation examples. The skill is a documentation reference - it shows users example commands but does not execute them.
False Positive: Hardcoded URLs
Scanner flagged 3 hardcoded URLs. These are legitimate Microsoft Learn documentation links and example curl commands for health check endpoints.
False Positive: Environment Variable Access
Scanner flagged 'process.env.PORT' as sensitive. This is standard Azure Container Apps documentation showing how to read the container port from environment variables.
Audited by: claude

Quality Score

50
Architecture
100
Maintainability
85
Content
50
Community
60
Security
91
Spec Compliance

What You Can Build

Debug Container App image pull failures

Diagnose why a container image fails to pull from Azure Container Registry and get step-by-step fix commands

Analyze application logs with KQL

Query Application Insights to find recent errors, failed requests, and slow performance issues

Fix cold start timeout issues

Identify and resolve slow first-request issues in Azure Container Apps by adjusting replica settings

Try These Prompts

Basic diagnostic request
My Azure Container App is failing to start. Help me diagnose the issue using the azure-diagnostics skill.
Image pull failure troubleshooting
I keep getting image pull errors in my Container App. How do I fix ACR authentication issues?
Log analysis with KQL
Help me write KQL queries to find errors in my Application Insights logs from the last hour.
Health probe investigation
My container keeps restarting due to health probe failures. What should I check?

Best Practices

  • Start with resource health checks before diving into detailed logs
  • Use systematic diagnosis flow: symptoms -> health -> logs -> metrics -> changes
  • Leverage AppLens MCP for AI-powered root cause analysis when available
  • Document all attempted remediation steps for future reference

Avoid

  • Do not skip health checks when investigating container restarts
  • Do not assume Azure service health without checking HealthResources first
  • Do not ignore provisioning state failures - these indicate deployment issues

Frequently Asked Questions

What does this skill actually do?
This skill provides troubleshooting guides, diagnostic commands, and KQL queries for Azure Container Apps. It does not execute commands but teaches you how to diagnose issues.
Can this skill fix my Azure issues?
No. This skill provides guidance and commands you can run. You must execute the Azure CLI commands yourself using Azure credentials.
What Azure services are supported?
Currently covers Azure Container Apps diagnostics including image pull, cold start, and health probe issues. More services coming soon.
Do I need Azure CLI installed?
Yes, you need Azure CLI installed to run the diagnostic commands shown. The skill provides the commands but you must have az CLI configured.
What is AppLens?
AppLens is an Azure MCP tool that provides AI-powered diagnostics. It can automatically detect issues and suggest remediation steps.
How do I query Azure Resource Graph?
Use the extension_cli_generate MCP tool with intent 'query Azure Resource Graph' or construct az graph query commands with KQL.