azure-diagnostics

The azure-diagnostics skill provides a structured framework for troubleshooting Azure production issues. It integrates with AppLens, Azure Monitor, and resource health tools to identify root causes for services including App Service, Function Apps, AKS, and messaging services like Event Hubs and Service Bus.

440.1K
Installs
6
Use cases
5/10
Quality

Is azure-diagnostics safe to install?

Review the source first

Review the source first: our audit of azure-diagnostics's source files found 4 shell commands, 0 external URLs, no file writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes Azure CLI commands and MCP tool calls that interact with live production infrastructure.

How we audit skills: our security review methodology.

Who is this skill for?

Cloud engineers, DevOps professionals, and site reliability engineers managing Azure production environments.

What can you do with it?

  • Diagnose high CPU or deployment failures in App Service
  • Troubleshoot AKS cluster, node, and pod connectivity issues
  • Analyze logs and metrics for Azure Function Apps
  • Investigate messaging SDK errors in Event Hubs and Service Bus
  • Check Azure resource health status
  • Execute KQL queries against Log Analytics workspaces

How good is this skill?

Quality score: 5/10. The skill provides clear, actionable diagnostic workflows and specific CLI commands for common Azure failure scenarios.

What does the skill file contain?

SKILL.md
# 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 App...

Frequently asked questions

Which Azure services does this skill support?

The skill supports App Service, Function Apps, AKS, Event Hubs, and Service Bus.

How does the skill perform AI-powered diagnostics?

It utilizes the mcp_azure_mcp_applens tool to run automated issue detection and root cause analysis.

Can this skill query logs?

Yes, it uses the mcp_azure_mcp_monitor tool to execute KQL queries against Log Analytics workspaces.

Data sourced from microsoft/azure-skills on GitHub. Install counts from skills.sh. The summary and security audit are derived from the skill's source files: every command and URL listed appears verbatim in the source.

Related skills

azure-deploy

433.6K

Developers and DevOps engineers deploying existing applications to Azure who require a structured, validated deployment process

The azure-deploy skill executes deployments for pre-configured Azure applications. It manages the deployment lifecycle using Azure Developer CLI (azd), Terraform, and Azure CLI commands, following a strict validation workflow that requires prior execution of azure-prepare and azure-validate.

highazuredeploymentmicrosoft

azure-ai

429.4K

Developers and AI agents requiring integration with Azure AI services for search, transcription, and synthesis tasks

The azure-ai skill provides tools for interacting with Azure AI services, including AI Search, Speech, OpenAI, and Document Intelligence. It supports search operations, speech-to-text, text-to-speech, and OCR through an MCP server interface.

highazureaimicrosoft

microsoft-foundry

429.2K

Developers building, deploying, and managing AI agents on Azure AI Foundry

The Microsoft Foundry skill provides a framework for the end-to-end lifecycle of AI agents, including scaffolding, deployment, evaluation, fine-tuning, and troubleshooting within Azure AI Foundry.

highazureai-agentsmicrosoft

systematic-debugging

173.2K

Software engineers and AI agents tasked with resolving bugs, test failures, or unexpected system behaviors

A structured methodology for debugging technical issues by prioritizing root cause identification over symptom-based patching. It mandates a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation, while providing specific protocols for handling persistent failures and architectural concerns.

highdebuggingtroubleshootingobra