Skip to content
TrustedSkillsbeta
Back to all skills

Azure Resource Health Diagnose

Official
github·vlatest·cloud·MIT

Quickly identifies and explains Azure resource health issues using GitHub's AI to suggest remediation steps.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add github/awesome-copilot --skill azure-resource-health-diagnose -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

github

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned github/awesome-copilot at 6c4d33b9cf.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6c4d33b9cf
Manifest
skills/azure-resource-health-diagnose/SKILL.md
Scanned
1 file, 276 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to diagnose the health status of Azure resources, providing insights into potential issues such as performance degradation, configuration errors, or resource failures. It leverages Azure Resource Health data to identify and report on the current state of cloud infrastructure components.

When to use it

  • When troubleshooting unexpected outages in Azure virtual machines or other resources.
  • Before deploying new workloads to ensure existing resources are healthy and stable.
  • During routine maintenance checks to proactively detect resource health issues.
  • After a deployment failure to identify if the issue stems from an unhealthy resource.

Key capabilities

  • Analyzes Azure Resource Health status for individual resources.
  • Identifies resource health events such as outages or degradations.
  • Provides actionable insights and recommendations based on health data.

Example prompts

  • "Check the health of my Azure virtual machine named 'web-server01'."
  • "What are the recent health issues reported for my Azure SQL database?"
  • "Diagnose why my Azure App Service is experiencing high latency."

Tips & gotchas

  • Ensure that your AI agent has access to Azure Resource Health API permissions.
  • This skill relies on real-time data, so results may vary based on current resource status and availability of health metrics.