Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoftdocs/azure-service-health
Expert knowledge for Azure Service Health development including troubleshooting, decision making, limits & quotas, security, configuration, and integrations & coding patterns.
Passed 8 of 15 test cases with the skill, and 2 of 15 without it.
and 9 more in the full report
10 fixed3 passed either way12 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When fetching full Microsoft documentation pages for Azure Service Health topics using HTTP tools or documentation tools, what specific query string parameter must be appended to the fetch URL?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the query parameter string from=learn-agent-skill. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill provides expert guidance for Azure Service Health. Covers troubleshooting, decision making, limits & quotas, security, 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 | L34-L38 | Understanding VM Resource Health annotations, diagnosing VM health issues, and troubleshooting platform or user-caused VM availability and performance problems |
| Decision Making | L39-L44 | Guidance on selecting and interpreting Azure retirement alerts, and mapping retirement notices to specific resources to assess impact and plan mitigation. |
| Limits & Quotas | L45-L49 | Details on how long Azure Service Health notifications are kept, their lifecycle stages, and retention behavior for different event types and channels |
| Security | L50-L58 | Managing who can see Azure Service Health and security advisories using tenant/subscription roles and RBAC, including configuring access scopes and viewing security-related notifications. |
| Configuration | L59-L66 | Configuring Service Health and Resource Health alerts via ARM/Bicep/PowerShell and querying Service Health data/fields with Azure Resource Graph. |
| Integrations & Coding Patterns | L67-L77 | Using APIs, Resource Graph, webhooks, and connectors (OpsGenie, PagerDuty, ServiceNow) to programmatically access, query, and route Azure Service Health and Security advisories |
| Topic | URL |
|---|---|
| Interpret and troubleshoot VM Resource Health annotations | https://learn.microsoft.com/en-us/azure/service-health/resource-health-vm-annotation |
| Topic | URL |
|---|---|
| Choose Azure retirement alert signals effectively | https://learn.microsoft.com/en-us/azure/service-health/service-retirement-alerting-guidance |
| Correlate retirement events to impacted Azure resources | https://learn.microsoft.com/en-us/azure/service-health/service-retirement-unified-impact-queries |
| Topic | URL |
|---|---|
| Understand lifecycle and retention of Service Health notifications | https://learn.microsoft.com/en-us/azure/service-health/service-health-notification-transitions |
test cases passed, vs 2 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.