[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DC22MS547TZ397YGQVMJT3":3,"skill-same:01M7DC22MS547TZ397YGQVMJT3":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DC22MS547TZ397YGQVMJT3","azure-fault-triage",null,"Azure fault triage. Use when an Azure app or resource is failing and the cause isn't known yet, such as an API returning 503s, a function that stopped firing, a latency spike at a given time, or a failed deployment. For shipping the fix through slots or revisions, use azure-blue-green-deploy.","stratisd-labs\u002Fcloud-agent-skills","stratisd-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F306447811?v=4","01M7DC1K5BT424WABZHANZ0XAG","Stratis D Labs","01M7DC1K6BNQRW9FYBSYZ2QRMB",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002Fazure\u002Fskills\u002Fazure-fault-triage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: azure-fault-triage\ndescription:\n  Azure fault triage. Use when an Azure app or resource is failing and the cause\n  isn't known yet, such as an API returning 503s, a function that stopped\n  firing, a latency spike at a given time, or a failed deployment. For shipping\n  the fix through slots or revisions, use azure-blue-green-deploy.\n---\n\n# Azure fault triage\n\nPropose a diagnosis and a fix; never restart, scale, roll back or change\nanything. Output the triage as described in the Output section and let the human\napply it, following `azure-propose-only`.\n\nLearn already covers the baseline. Read these through the Learn MCP instead of\nrestating them:\n\n- [Resource Health overview][rh]: availability states and what each means.\n- [Activity log][activity]: what it records and how to filter it.\n- [App Service diagnostics][as-diag]: the Diagnose and solve problems detectors.\n- [Container Apps deployment failures][aca-fail]: revision states, probes and\n  system logs.\n\nThis skill adds the order to look in, what clears the platform, and the first\nchecks per service that Learn spreads across pages. Shipping the fix is covered\nby `azure-blue-green-deploy`.\n\n## Precedence\n\n1. A runbook, on-call guide or dashboard the project already has wins. Look in\n   its `AGENTS.md`, docs and alert rules, and follow its order.\n2. Without one, use the triage order below.\n\n## Triage order\n\nWork in this order. Most incidents are the platform or a change, and both are\ncheaper to confirm than an application cause.\n\n1. **Frame.** The symptom, the affected resource, when it started (in UTC), and\n   what the human says changed. A start time is required: ask for one rather\n   than querying \"now\". The window runs from 2 hours before the start to the\n   end, or to now if it's ongoing.\n2. **Rule out the platform.** Service Health events that overlap the window in\n   the resource's region, then the resource's Resource Health history. An\n   overlapping incident or an `Unavailable` state with a platform cause ends the\n   search: the plan is to wait, fail over, or open a ticket, not to change the\n   app.\n3. **What changed.** The resource group's activity log and deployment history\n   from 24 hours before the start to its end. A change that lands minutes before\n   the start is the leading hypothesis until the evidence clears it.\n4. **Evidence.** Metrics and logs for the window, per service below.\n5. **Rank hypotheses** by the evidence for each, and give each the query that\n   confirms or rules it out.\n6. **Plan** the fix, and the check that shows it worked.\n\n## First checks per service\n\n### App Service and Functions\n\n- **Platform restarts.** [Routine maintenance][maint] restarts apps, and those\n  restarts don't reliably appear in the activity log. Read Resource Health\n  history, and ask the human to run the Web App Restarted detector under\n  Diagnose and solve problems. A restart lines up with 5xx bursts and cold\n  starts. On a single instance, it's downtime.\n- **Slot swaps.** A swap restarts the target's workers. Look for\n  `Microsoft.Web\u002Fsites\u002Fslots\u002Fslotsswap\u002Faction` in the activity log; one just\n  before the start makes the swapped build the first suspect. To roll back, hand\n  over to `azure-blue-green-deploy`.\n- **SNAT exhaustion.** Intermittent 5xx and time-outs to dependencies, with\n  normal CPU, point to it: each instance starts with 128 SNAT ports, used up by\n  repeated connections to the same address and port. Check dependency latency\n  first: slow backends hold connections open, so exhaustion is usually the\n  symptom. Ask the human to run the SNAT Port Exhaustion detector; there's no\n  metric for it.\n- **A function app that stopped firing** right after a rename, a new slot, or a\n  second app on the same storage account: check for a host ID collision. Ask the\n  human to run the Function App Down or Reporting Errors detector, which checks\n  for them. See [host ID collisions][hostid].\n\n### Container Apps\n\n- **Revision state first.** List revisions with their health, running and\n  provisioning state. A new revision that's `Degraded` or still provisioning\n  points to probes, the image or the target port.\n- **Probes.** System logs show probe failures. With ingress on and no probes\n  configured, defaults apply; a slow-starting app then fails them. Compare the\n  probe port with the ingress `targetPort`.\n\n## Gotchas\n\n- **Resource Health in Resource Graph covers VMs only.** `HealthResources`\n  returns availability for virtual machines; for App Service, Functions,\n  Container Apps and the rest, read the resource's history through the Resource\n  Health API or the Azure MCP.\n- **A clean activity log doesn't clear the platform.** It records control plane\n  operations: deployments, swaps, scaling, config writes. Platform maintenance\n  and crashes don't reliably appear there.\n- **`az monitor activity-log list` reads 6 hours and 50 events by default.**\n  Pass `--start-time`, `--end-time` and `--max-events`, or the change that\n  caused a morning incident is cut off. The Azure MCP's activity log command\n  takes `hours` back from now instead: set it to reach 24 hours before the\n  start.\n- **`az monitor log-analytics query` reads all data by default.** Without\n  `--timespan`, a query scans the table's whole retention. Bound every query to\n  the window.\n- **Metrics and log queries need the window and the workspace GUID.** See [Azure\n  Monitor queries][monitor-queries].\n- **A restart is a mitigation, not a diagnosis.** It clears temporary files,\n  process state and the instance the fault lived on. Capture the evidence first,\n  and plan the restart after the checkpoint with what it destroys in its blast\n  radius.\n- **Use UTC everywhere.** Activity log, metrics and logs are in UTC; convert the\n  human's start time once, in step 1, and say so.\n\n## Checks before proposing\n\nAll read-only. Prefer the Azure MCP's `resourcehealth` and `monitor` tools when\nthey're loaded; these are the CLI equivalents. Run the ones that apply:\n\n```bash\n# Which account and subscription is this?\naz account show --query '{sub: id, name: name, user: user.name}'\n\n# Platform: Service Health events (resource-graph extension); keep the\n# ones whose impact overlaps the window and the resource's region\naz graph query -q \"ServiceHealthResources\n  | where type =~ 'Microsoft.ResourceHealth\u002Fevents'\n  | project title = properties.Title, kind = properties.EventType,\n    status = properties.Status, start = properties.ImpactStartTime,\n    end = properties.ImpactMitigationTime\"\n\n# Platform: the resource's Resource Health history, any resource type\naz rest --method get --url \"https:\u002F\u002Fmanagement.azure.com\u003CRESOURCE_ID>\\\n\u002Fproviders\u002FMicrosoft.ResourceHealth\u002FavailabilityStatuses\\\n?api-version=2025-05-01\" \\\n  --query \"value[].{state: properties.availabilityState,\n    at: properties.occuredTime, cause: properties.reasonType,\n    summary: properties.summary}\"\n\n# Changes: control plane operations, 24 hours before the start to the end\naz monitor activity-log list --resource-group \u003CRG> \\\n  --start-time \u003CSTART_MINUS_24H> --end-time \u003CEND> --max-events 500 \\\n  --query \"[?status.value=='Succeeded' || status.value=='Failed'].{\n    at: eventTimestamp, op: operationName.value,\n    status: status.value, by: caller}\"\n\n# Changes: deployments, and why a failed one failed\naz deployment group list --resource-group \u003CRG> \\\n  --query \"[].{name: name, state: properties.provisioningState,\n    at: properties.timestamp}\"\naz deployment operation group list --resource-group \u003CRG> \\\n  --name \u003CDEPLOYMENT> \\\n  --query \"[?properties.provisioningState=='Failed'].properties.statusMessage\"\n\n# Evidence, App Service and Functions: 5xx and latency over the window\naz monitor metrics list --resource \u003CRESOURCE_ID> \\\n  --metrics Http5xx Requests --aggregation Total \\\n  --start-time \u003CSTART> --end-time \u003CEND> --interval 5m\naz monitor metrics list --resource \u003CRESOURCE_ID> \\\n  --metrics HttpResponseTime --aggregation Average \\\n  --start-time \u003CSTART> --end-time \u003CEND> --interval 5m\n\n# Evidence: failed requests and slow dependencies, workspace-based App Insights\naz monitor log-analytics query --workspace \u003CWORKSPACE_GUID> \\\n  --timespan \u003CSTART>\u002F\u003CEND> \\\n  --analytics-query \"AppRequests | where Success == false\n    | summarize failed = count() by ResultCode, bin(TimeGenerated, 5m)\"\naz monitor log-analytics query --workspace \u003CWORKSPACE_GUID> \\\n  --timespan \u003CSTART>\u002F\u003CEND> \\\n  --analytics-query \"AppDependencies\n    | summarize p95 = percentile(DurationMs, 95), failed = countif(not(Success))\n      by Target, bin(TimeGenerated, 5m)\"\n\n# Functions: runtime errors, a host ID collision among them\naz monitor log-analytics query --workspace \u003CWORKSPACE_GUID> \\\n  --timespan \u003CSTART>\u002F\u003CEND> \\\n  --analytics-query \"AppTraces | where SeverityLevel >= 3\n    | project TimeGenerated, AppRoleName, Message\"  # verify: AZFD0004 text\n\n# Container Apps: revision state, probes, then platform events\naz containerapp revision list --resource-group \u003CRG> --name \u003CAPP> \\\n  --query \"[].{rev: name, health: properties.healthState,\n    running: properties.runningState,\n    provisioning: properties.provisioningState,\n    traffic: properties.trafficWeight}\"\naz containerapp revision show --resource-group \u003CRG> --name \u003CAPP> \\\n  --revision \u003CREVISION> --query \"properties.template.containers[].probes\"\naz containerapp logs show --resource-group \u003CRG> --name \u003CAPP> \\\n  --type system --tail 50\n```\n\n`--timespan` takes `\u003CSTART>\u002F\u003CEND>` in ISO 8601, UTC. The Service Health query\nfollows Learn's [Resource Graph samples for Service Health][rg-sh]; the Resource\nHealth call follows [Availability Statuses - List][rh-api].\n\n## Output\n\nGive, in order:\n\n1. **Frame**: the symptom, the resource, the window in UTC, and what the human\n   said changed.\n2. **Checks**: which checks ran, in the triage order, and what each returned, or\n   why it was skipped. Platform and change checks come first.\n3. **Timeline**: the changes, health transitions and metric shifts in the\n   window, in time order, against the start time.\n4. **Hypotheses**: ranked, each with the evidence for and against, the query\n   that confirms or rules it out, and a confidence of high, medium or low.\n5. **Most likely cause**: one line, with the evidence that decides it, or\n   \"unknown\" and the check that would decide it.\n6. **Plan**: one plan in the `azure-propose-only` format. Mitigation first, then\n   the fix. Its verification step names the metric or query that should return\n   to the baseline, and the value it had before the start.\n\nFlag these as blockers, not notes: no start time, a platform incident that\noverlaps the window, a check that couldn't run for the platform or the changes,\nand a fix proposed with no evidence that ranks it first.\n\nLast verified: 2026-10-22\n\n[hostid]: ..\u002F..\u002Freference\u002Fazure-functions\u002Fconfiguration.md\n[monitor-queries]: ..\u002F..\u002Freference\u002Fazure-monitor\u002Fqueries.md\n[rh]: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fservice-health\u002Fresource-health-overview\n[activity]:\n  https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-monitor\u002Ffundamentals\u002Factivity-log\n[rg-sh]: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fservice-health\u002Fresource-graph-samples\n[rh-api]:\n  https:\u002F\u002Flearn.microsoft.com\u002Frest\u002Fapi\u002Fresourcehealth\u002Favailability-statuses\u002Flist\n[maint]:\n  https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fapp-service\u002Froutine-maintenance-downtime\n[as-diag]: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fapp-service\u002Foverview-diagnostics\n[aca-fail]:\n  https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fcontainer-apps\u002Ftroubleshoot-deployment-errors\n","# Azure fault triage\n\nPropose a diagnosis and a fix; never restart, scale, roll back or change\nanything. Output the triage as described in the Output section and let the human\napply it, following `azure-propose-only`.\n\nLearn already covers the baseline. Read these through the Learn MCP instead of\nrestating them:\n\n- [Resource Health overview][rh]: availability states and what each means.\n- [Activity log][activity]: what it records and how to filter it.\n- [App Service diagnostics][as-diag]: the Diagnose and solve problems detectors.\n- [Container Apps deployment failures][aca-fail]: revision states, probes and\n  system logs.\n\nThis skill adds the order to look in, what clears the platform, and the first\nchecks per service that Learn spreads across pages. Shipping the fix is covered\nby `azure-blue-green-deploy`.\n\n## Precedence\n\n1. A runbook, on-call guide or dashboard the project already has wins. Look in\n   its `AGENTS.md`, docs and alert rules, and follow its order.\n2. Without one, use the triage order below.\n\n## Triage order\n\nWork in this order. Most incidents are the platform or a change, and both are\ncheaper to confirm than an application cause.\n\n1. **Frame.** The symptom, the affected resource, when it started (in UTC), and\n   what the human says changed. A start time is required: ask for one rather\n   than querying \"now\". The window runs from 2 hours before the start to the\n   end, or to now if it's ongoing.\n2. **Rule out the platform.** Service Health events that overlap the window in\n   the resource's region, then the resource's Resource Health history. An\n   overlapping incident or an `Unavailable` state with a platform cause ends the\n   search: the plan is to wait, fail over, or open a ticket, not to change the\n   app.\n3. **What changed.** The resource group's activity log and deployment history\n   from 24 hours before the start to its end. A change that lands minutes before\n   the start is the leading hypothesis until the evidence clears it.\n4. **Evidence.** Metrics and logs for the window, per service below.\n5. **Rank hypotheses** by the evidence for each, and give each the query that\n   confirms or rules it out.\n6. **Plan** the fix, and the check that shows it worked.\n\n## First checks per service\n\n### App Service and Functions\n\n- **Platform restarts.** [Routine maintenance][maint] restarts apps, and those\n  restarts don't reliably appear in the activity log. Read Resource Health\n  history, and ask the human to run the Web App Restarted detector under\n  Diagnose and solve problems. A restart lines up with 5xx bursts and cold\n  starts. On a single instance, it's downtime.\n- **Slot swaps.** A swap restarts the target's workers. Look for\n  `Microsoft.Web\u002Fsites\u002Fslots\u002Fslotsswap\u002Faction` in the activity log; one just\n  before the start makes the swapped build the first suspect. To roll back, hand\n  over to `azure-blue-green-deploy`.\n- **SNAT exhaustion.** Intermittent 5xx and time-outs to dependencies, with\n  normal CPU, point to it: each instance starts with 128 SNAT ports, used up by\n  repeated connections to the same address and port. Check dependency latency\n  first: slow backends hold connections open, so exhaustion is usually the\n  symptom. Ask the human to run the SNAT Port Exhaustion detector; there's no\n  metric for it.\n- **A function app that stopped firing** right after a rename, a new slot, or a\n  second app on the same storage account: check for a host ID collision. Ask the\n  human to run the Function App Down or Reporting Errors detector, which checks\n  for them. See [host ID collisions][hostid].\n\n### Container Apps\n\n- **Revision state first.** List revisions with their health, running and\n  provisioning state. A new revision that's `Degraded` or still provisioning\n  points to probes, the image or the target port.\n- **Probes.** System logs show probe failures. With ingress on and no probes\n  configured, defaults apply; a slow-starting app then fails them. Compare the\n  probe port with the ingress `targetPort`.\n\n## Gotchas\n\n- **Resource Health in Resource Graph covers VMs only.** `HealthResources`\n  returns availability for virtual machines; for App Service, Functions,\n  Container Apps and the rest, read the resource's history through the Resource\n  Health API or the Azure MCP.\n- **A clean activity log doesn't clear the platform.** It records control plane\n  operations: deployments, swaps, scaling, config writes. Platform maintenance\n  and crashes don't reliably appear there.\n- **`az monitor activity-log list` reads 6 hours and 50 events by default.**\n  Pass `--start-time`, `--end-time` and `--max-events`, or the change that\n  caused a morning incident is cut off. The Azure MCP's activity log command\n  takes `hours` back from now instead: set it to reach 24 hours before the\n  start.\n- **`az monitor log-analytics query` reads all data by default.** Without\n  `--timespan`, a query scans the table's whole retention. Bound every query to\n  the window.\n- **Metrics and log queries need the window and the workspace GUID.** See [Azure\n  Monitor queries][monitor-queries].\n- **A restart is a mitigation, not a diagnosis.** It clears temporary files,\n  process state and the instance the fault lived on. Capture the evidence first,\n  and plan the restart after the checkpoint with what it destroys in its blast\n  radius.\n- **Use UTC everywhere.** Activity log, metrics and logs are in UTC; convert the\n  human's start time once, in step 1, and say so.\n\n## Checks before proposing\n\nAll read-only. Prefer the Azure MCP's `resourcehealth` and `monitor` tools when\nthey're loaded; these are the CLI equivalents. Run the ones that apply:\n\n```bash\n# Which account and subscription is this?\naz account show --query '{sub: id, name: name, user: user.name}'\n\n# Platform: Service Health events (resource-graph extension); keep the\n# ones whose impact overlaps the window and the resource's region\naz graph query -q \"ServiceHealthResources\n  | where type =~ 'Microsoft.ResourceHealth\u002Fevents'\n  | project title = properties.Title, kind = properties.EventType,\n    status = properties.Status, start = properties.ImpactStartTime,\n    end = properties.ImpactMitigationTime\"\n\n# Platform: the resource's Resource Health history, any resource type\naz rest --method get --url \"https:\u002F\u002Fmanagement.azure.com\u003CRESOURCE_ID>\\\n\u002Fproviders\u002FMicrosoft.ResourceHealth\u002FavailabilityStatuses\\\n?api-version=2025-05-01\" \\\n  --query \"value[].{state: properties.availabilityState,\n    at: properties.occuredTime, cause: properties.reasonType,\n    summary: properties.summary}\"\n\n# Changes: control plane operations, 24 hours before the start to the end\naz monitor activity-log list --resource-group \u003CRG> \\\n  --start-time \u003CSTART_MINUS_24H> --end-time \u003CEND> --max-events 500 \\\n  --query \"[?status.value=='Succeeded' || status.value=='Failed'].{\n    at: eventTimestamp, op: operationName.value,\n    status: status.value, by: caller}\"\n\n# Changes: deployments, and why a failed one failed\naz deployment group list --resource-group \u003CRG> \\\n  --query \"[].{name: name, state: properties.provisioningState,\n    at: properties.timestamp}\"\naz deployment operation group list --resource-group \u003CRG> \\\n  --name \u003CDEPLOYMENT> \\\n  --query \"[?properties.provisioningState=='Failed'].properties.statusMessage\"\n\n# Evidence, App Service and Functions: 5xx and latency over the window\naz monitor metrics list --resource \u003CRESOURCE_ID> \\\n  --metrics Http5xx Requests --aggregation Total \\\n  --start-time \u003CSTART> --end-time \u003CEND> --interval 5m\naz monitor metrics list --resource \u003CRESOURCE_ID> \\\n  --metrics HttpResponseTime --aggregation Average \\\n  --start-time \u003CSTART> --end-time \u003CEND> --interval 5m\n\n# Evidence: failed requests and slow dependencies, workspace-based App Insights\naz monitor log-analytics query --workspace \u003CWORKSPACE_GUID> \\\n  --timespan \u003CSTART>\u002F\u003CEND> \\\n  --analytics-query \"AppRequests | where Success == false\n    | summarize failed = count() by ResultCode, bin(TimeGenerated, 5m)\"\naz monitor log-analytics query --workspace \u003CWORKSPACE_GUID> \\\n  --timespan \u003CSTART>\u002F\u003CEND> \\\n  --analytics-query \"AppDependencies\n    | summarize p95 = percentile(DurationMs, 95), failed = countif(not(Success))\n      by Target, bin(TimeGenerated, 5m)\"\n\n# Functions: runtime errors, a host ID collision among them\naz monitor log-analytics query --workspace \u003CWORKSPACE_GUID> \\\n  --timespan \u003CSTART>\u002F\u003CEND> \\\n  --analytics-query \"AppTraces | where SeverityLevel >= 3\n    | project TimeGenerated, AppRoleName, Message\"  # verify: AZFD0004 text\n\n# Container Apps: revision state, probes, then platform events\naz containerapp revision list --resource-group \u003CRG> --name \u003CAPP> \\\n  --query \"[].{rev: name, health: properties.healthState,\n    running: properties.runningState,\n    provisioning: properties.provisioningState,\n    traffic: properties.trafficWeight}\"\naz containerapp revision show --resource-group \u003CRG> --name \u003CAPP> \\\n  --revision \u003CREVISION> --query \"properties.template.containers[].probes\"\naz containerapp logs show --resource-group \u003CRG> --name \u003CAPP> \\\n  --type system --tail 50\n```\n\n`--timespan` takes `\u003CSTART>\u002F\u003CEND>` in ISO 8601, UTC. The Service Health query\nfollows Learn's [Resource Graph samples for Service Health][rg-sh]; the Resource\nHealth call follows [Availability Statuses - List][rh-api].\n\n## Output\n\nGive, in order:\n\n1. **Frame**: the symptom, the resource, the window in UTC, and what the human\n   said changed.\n2. **Checks**: which checks ran, in the triage order, and what each returned, or\n   why it was skipped. Platform and change checks come first.\n3. **Timeline**: the changes, health transitions and metric shifts in the\n   window, in time order, against the start time.\n4. **Hypotheses**: ranked, each with the evidence for and against, the query\n   that confirms or rules it out, and a confidence of high, medium or low.\n5. **Most likely cause**: one line, with the evidence that decides it, or\n   \"unknown\" and the check that would decide it.\n6. **Plan**: one plan in the `azure-propose-only` format. Mitigation first, then\n   the fix. Its verification step names the metric or query that should return\n   to the baseline, and the value it had before the start.\n\nFlag these as blockers, not notes: no start time, a platform incident that\noverlaps the window, a check that couldn't run for the platform or the changes,\nand a fix proposed with no evidence that ranks it first.\n\nLast verified: 2026-10-22\n\n[hostid]: ..\u002F..\u002Freference\u002Fazure-functions\u002Fconfiguration.md\n[monitor-queries]: ..\u002F..\u002Freference\u002Fazure-monitor\u002Fqueries.md\n[rh]: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fservice-health\u002Fresource-health-overview\n[activity]:\n  https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-monitor\u002Ffundamentals\u002Factivity-log\n[rg-sh]: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fservice-health\u002Fresource-graph-samples\n[rh-api]:\n  https:\u002F\u002Flearn.microsoft.com\u002Frest\u002Fapi\u002Fresourcehealth\u002Favailability-statuses\u002Flist\n[maint]:\n  https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fapp-service\u002Froutine-maintenance-downtime\n[as-diag]: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fapp-service\u002Foverview-diagnostics\n[aca-fail]:\n  https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fcontainer-apps\u002Ftroubleshoot-deployment-errors\n",{"name":5,"description":7},"main","22edd1a5b1742a76ef28193e3a6d5e3f60672adf","azure\u002Fskills\u002Fazure-fault-triage","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills","https:\u002F\u002Fgithub.com\u002Fstratisd-labs","https:\u002F\u002Fstratis.dermanoutsos.com","The D is not a One Piece reference... :smile:","2026-10-26 01:24:43",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stratisd-labs\u002Fcloud-agent-skills --skill azure-fault-triage",{"tool":38,"command":39},"bunx","bunx skills add stratisd-labs\u002Fcloud-agent-skills --skill azure-fault-triage",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stratisd-labs\u002Fcloud-agent-skills --skill azure-fault-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002Fazure\u002Fskills\u002Fazure-fault-triage\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7DC2KP6PTKPKHJHE24T394M","azure-resource-tagging","Azure resource tagging. Use when choosing tags for a new Azure resource or resource group, when writing Bicep, Terraform or az CLI that creates resources, or when auditing existing tags for gaps and inconsistent values that break cost reports. For names, use azure-resource-naming.","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002Fazure\u002Fskills\u002Fazure-resource-tagging\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7DC2DZ83MARN1QMF3ZEJ80Z","azure-resource-naming","Azure resource naming. Use when choosing a name for a new Azure resource, resource group or deployment slot, when writing Bicep, Terraform or az CLI that creates resources, or when reviewing existing names for consistency. For tags, use azure-resource-tagging.","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002Fazure\u002Fskills\u002Fazure-resource-naming\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7DC28HJE4AQG64NS6G1YZ2J","azure-propose-only","Azure change planning, propose-only. Use when a task would create, change, scale, restart, tag, rotate or delete anything in Azure, when writing the plan another azure-* skill outputs, or when deciding whether an az command is safe to run.","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002Fazure\u002Fskills\u002Fazure-propose-only\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DC1XXRYC0257GBHH6Q7JR6","azure-cost-review","Azure cost review. Use when asked to cut an Azure bill, to explain why Azure costs jumped, to find what can be shut down or deleted, or to check whether a SKU is oversized. For tags that attribute cost, use azure-resource-tagging.","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002Fazure\u002Fskills\u002Fazure-cost-review\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DC1SKFW9HQDPQHX5FT0J7Y","azure-blue-green-deploy","Azure blue-green and zero-downtime releases. Use when planning a release through deployment slots or Container Apps revisions, when swapping a slot into production, when splitting traffic between an old and a new version, or when rolling back the last release. For slot names, use azure-resource-naming.","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002Fazure\u002Fskills\u002Fazure-blue-green-deploy\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DC1MF1X1X07FY1D5FKF8S4","create-skill","Create, restructure or change an agent skill in this cloud-agent-skills repo, such as a new azure-* skill under azure\u002Fskills\u002F. Use when adding a skill to a plugin, turning notes into a skill, reshaping an existing skill to the repo's standard structure, or changing what an existing skill tells the agent to do. Not for skills in other repos.","https:\u002F\u002Fgithub.com\u002Fstratisd-labs\u002Fcloud-agent-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[],[]]