apex-azure-diagnostics

apex-azure-diagnostics is a skill for Claude Code from jonathan-vella/apex-accelerator. It costs 119 tokens per session (1,800 once invoked), scanned C, original, MIT.

An Azure production troubleshooting workflow for Container Apps and Function Apps, including resource health checks and log analysis with KQL. It is designed to investigate failures such as image pulls, cold starts, health probes, invocations, and timeouts.

In plain words
What is it for?
Use it to inspect Azure service health, analyze App Insights or Log Analytics data, and investigate application errors and failed deployments.
Why use it?
It provides a structured way to find the cause of an incident instead of changing resources without evidence. It keeps diagnosis separate from remediation, which may require additional approval.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit Use it to inspect Azure service health, analyze App Insights or Log Analytics data, and investigate application errors and failed deployments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonathan-vella/apex-accelerator/apex-azure-diagnostics
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 jonathan-vella/apex-accelerator --skill apex-azure-diagnostics
Clone the repo
git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: Claude Code.

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.

agentmods badge for apex-azure-diagnostics

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-diagnostics/github.svg)](https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-diagnostics)
Your own site
<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-diagnostics"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-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.

agentmods 80×15 button for apex-azure-diagnostics

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-diagnostics"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-diagnostics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,800 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00119 $0.01800
Opus 5.5 $0.00048 $0.00720
Sonnet 5.5 $0.00024 $0.00360
Haiku 4.5 $0.00012 $0.00180

Measured 22d ago against content hash 3f9ac0daeeee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

apex-azure-diagnostics scanned grade C with 1 finding 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 22d ago.

The scan reads SKILL.md. This mod also ships 12 executable files (scripts/aks-baseline.ps1, scripts/aks-baseline.sh, scripts/appservice-diagnostics.ps1, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

not a healthy result. Do not dump credentials or app settings into reports.
.github/skills/apex-azure-diagnostics/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 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
  • Troubleshoot Azure Function Apps (invocation failures, timeouts, binding errors)
  • Find the App Insights or Log Analytics workspace linked to a Function App
  • Troubleshoot App Service issues (high CPU, deployment failures, crashes, slow responses, TLS/custom domains)
  • Troubleshoot AKS clusters, nodes, pods, ingress, DNS or upgrades
  • Troubleshoot Azure VM connectivity (RDP/SSH failures, NSG or firewall blocks, VM agent issues)
  • Troubleshoot Event Hubs and Service Bus SDK errors (AMQP failures, lock lost, connectivity)

Rules

  1. Start with systematic diagnosis flow
  2. Use AppLens (MCP) for AI-powered diagnostics when available
  3. Check resource health before deep-diving into logs
  4. Select appropriate troubleshooting guide based on service type
  5. Document findings and attempted remediation steps
  6. Diagnose only the approved scope; obtain separate approval before remediation
  7. Default to read-only. Restarts, redeploys, run-command, credential resets, NSG changes, cordon/drain and node debug pods (run-ig with --approve) each need explicit approval
  8. Never print secret values: list app setting names only, and never pass passwords through chat

Prerequisites

  • Confirm resource IDs, subscription, incident window and read access.
  • Use available Azure CLI or MCP capabilities; unavailable telemetry is a gap, not a healthy result. Do not dump credentials or app settings into reports.

Read the full file on GitHub · 179 lines

Files

What ships with it

52 files 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.

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.

  1. 22d ago Changed · +31 lines · +19 tokens per session 3f9ac0daeeee
  2. 23d ago First seen · 148 lines · 100 tokens per session scan C 21493bc93690

Subscribe to this mod's changes

apex-azure-diagnostics is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 119 tokens to every session and 1,800 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.

Related

Other skills, from other repositories

azure-kubernetes-automatic-readiness

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic…

microsoft/skills · 87 tokens

dynamo-interconnect-check

Validate that a Dynamo deployment's NIXL/UCX/NCCL interconnect is ready for disaggregated serving over RDMA/NVLink. Use after recipe-runner brings a deployment up (especially disagg/multi-node) to confirm the KV transport is correct; use troubleshoot for diagnosing already-failed pods.

NVIDIA/skills · 71 tokens

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, container app 503 or target port mismatch, troubleshoot functions, function…

microsoft/skills · 189 tokens

extracting-code-structure

Use when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files.

SebastienDegodez/copilot-instructions · 39 tokens

dynamo-troubleshoot

Diagnose failed or unhealthy Dynamo deployments. Use when pods, model-cache jobs, PVCs, workers, frontend/router health, endpoints, or benchmark jobs fail; use recipe-runner/router-starter before this for normal bring-up.

NVIDIA/skills · 52 tokens

forge-diagnose

Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".

tonone-ai/tonone · 63 tokens