From azure-agent-skills
Guides Azure Impact Reporting development including troubleshooting connectors, configuring alert integrations, and coding patterns for Monitor alerts, Logic Apps, Service Health, and HPC Guest Health.
How this skill is triggered — by the user, by Claude, or both
Slash command
/azure-agent-skills:azure-impact-reportingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides expert guidance for Azure Impact Reporting. Covers troubleshooting, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.
This skill provides expert guidance for Azure Impact Reporting. Covers troubleshooting, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
mcp_microsoftdocs:microsoft_docs_fetch with query string from=learn-agent-skill. Returns Markdown.fetch_webpage with query string from=learn-agent-skill&accept=text/markdown. Returns Markdown.| Category | Lines | Description |
|---|---|---|
| Troubleshooting | L31-L35 | Diagnosing and fixing Azure Impact Reporting connector failures and resolving Azure HPC Guest Health Reporting issues, errors, and data/health reporting problems. |
| Configuration | L36-L42 | Configuring Azure Impact Reporting: creating alert connectors and retrieving valid impact and HPC Guest Health category values for correct classification. |
| Integrations & Coding Patterns | L43-L49 | Patterns and examples for integrating Impact Reporting with Azure Monitor alerts, Logic Apps, diagnostic logs, Service Health, and APIs (sending, attaching data, and viewing insights). |
| Topic | URL |
|---|---|
| Troubleshoot Azure Impact Reporting connectors | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/connectors-troubleshooting-guide |
| Topic | URL |
|---|---|
| Create Azure Impact Reporting connectors for alerts | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/create-azure-monitor-connector |
| Use valid HPC Guest Health impact categories | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/guest-health-impact-categories |
| Retrieve valid Azure Impact Reporting categories | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/view-impact-categories |
| Topic | URL |
|---|---|
| Integrate Azure Monitor alerts with Impact Reporting | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/azure-monitor-connector |
| Use Logic Apps to send Azure impact reports | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/creating-logic-app |
| Attach diagnostic log files to Guest Health reports | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/guest-health-log-upload |
| Report Azure workload impact via Service Health and API | https://learn.microsoft.com/en-us/azure/azure-impact-reporting/report-impact |
npx claudepluginhub microsoftdocs/agent-skills --plugin azure-agent-skillsProvides expert guidance for Azure Service Health: troubleshooting VM Resource Health, configuring ARM/Bicep alerts, routing alerts via APIs/webhooks, and managing access with RBAC.
Investigates Azure operational health using Monitor, Log Analytics, Application Insights, KQL triage, alert rules, workbooks, and telemetry-gap analysis for incident and posture investigations.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.