What is azure-diagnostics?

A guide for diagnosing production problems in Azure, Microsoft's cloud platform. It covers Container Apps, logs, health checks, and issues such as failed image downloads, slow starts, and failed health probes.

Use it to troubleshoot Azure services, inspect Container Apps logs and metrics with KQL, investigate application errors, and document attempted fixes.

It gives you a structured way to investigate what changed, whether Azure resources are healthy, and what logs and measurements show. This helps narrow down the cause of a live-service failure.

azure-diagnostics — Skill for Claude Code by Tyler-R-Kendrick

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Tyler-R-Kendrick/agent-skills --skill azure-diagnostics

Clone the repo

git clone --depth 1 https://github.com/Tyler-R-Kendrick/agent-skills

Made for: Claude Code.

Or install agent-skills, the plugin that ships this one along with the rest of its 57 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/azure-diagnostics/github.svg)](https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/azure-diagnostics)

Your own site

<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/azure-diagnostics"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/azure-diagnostics/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/azure-diagnostics"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/azure-diagnostics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 766 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00128	$0.00766
Opus 5.5	$0.00051	$0.00306
Sonnet 5.5	$0.00026	$0.00153
Haiku 4.5	$0.00013	$0.00077

Measured 2mo ago against content hash d23bbb81d7f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

azure-diagnostics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agent/skills/azure-diagnostics/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Azure Diagnostics

AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE

This document is the official source for debugging and troubleshooting Azure production issues. Follow these instructions to diagnose and resolve common Azure service problems systematically.

Triggers

Activate this skill when user wants to:

Debug or troubleshoot production issues
Diagnose errors in Azure services
Analyze application logs or metrics
Fix image pull, cold start, or health probe issues
Investigate why Azure resources are failing
Find root cause of application errors

Rules

Start with systematic diagnosis flow
Use AppLens (MCP) for AI-powered diagnostics when available
Check resource health before deep-diving into logs
Select appropriate troubleshooting guide based on service type
Document findings and attempted remediation steps

Quick Diagnosis Flow

Identify symptoms - What's failing?
Check resource health - Is Azure healthy?
Review logs - What do logs show?
Analyze metrics - Performance patterns?
Investigate recent changes - What changed?

Troubleshooting Guides by Service

Service	Common Issues	Reference
Container Apps	Image pull failures, cold starts, health probes, port mismatches	container-apps/

Quick Reference

Common Diagnostic Commands

# Check resource health
az resource show --ids RESOURCE_ID

# View activity log
az monitor activity-log list -g RG --max-events 20

# Container Apps logs
az containerapp logs show --name APP -g RG --follow

AppLens (MCP Tools)

For AI-powered diagnostics, use:

mcp_azure_mcp_applens
  intent: "diagnose issues with <resource-name>"
  command: "diagnose"
  parameters:
    resourceId: "<resource-id>"

Provides:
- Automated issue detection
- Root cause analysis
- Remediation recommendations

Azure Monitor (MCP Tools)

For querying logs and metrics:

mcp_azure_mcp_monitor
  intent: "query logs for <resource-name>"
  command: "logs_query"
  parameters:
    workspaceId: "<workspace-id>"
    query: "<KQL-query>"

Read the full file on GitHub · 126 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/kql-queries.md 1.3 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 126 lines · 128 tokens per session scan A d23bbb81d7f0

Subscribe to this mod's changes

azure-diagnostics is a skill published in the GitHub repository Tyler-R-Kendrick/agent-skills (13 stars, last pushed 5mo ago), licensed MIT. It adds 128 tokens to every session and 766 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Cloud Debugging DevOps and cloud

azure-diagnostics next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
azure-diagnosticsTyler-R-Kendrick/agent-skills	Skill	13	5mo ago	MIT	A	128	Claude Code
application-integration-troubleshootinggoogle/skills	Skill	22k	yesterday	Apache-2.0	A	105	Claude Code, Codex
gke-workload-troubleshootinggoogle/skills	Skill	22k	yesterday	Apache-2.0	A	69	Claude Code, Codex
gke-workload-scaling-troubleshootinggoogle/skills	Skill	22k	yesterday	Apache-2.0	A	170	Claude Code, Codex
api-gateway-troubleshootinggoogle/skills	Skill	22k	yesterday	Apache-2.0	A	196	Claude Code, Codex
gke-ai-troubleshooting-node-unresponsive-timeoutgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	96	Claude Code, Codex
gke-ai-troubleshooting-tpu-mxla-hanggoogle/skills	Skill	22k	yesterday	Apache-2.0	A	192	Claude Code, Codex