What problem does it solve? Cloud incidents are often misdiagnosed because teams conflate resource existence, deployment success, configuration validity, and actual user-facing service health. This Skill provides a disciplined investigation pipeline that separates these claims, so outages, failed deployments, quota issues, and configuration drift are resolved from evidence rather than guesswork. ## Core Features & Use Cases - Structured Investigation Pipeline: A 10-step workflow covering scope confirmation, provider and resource health, deployment and activity logs, runtime metrics, dependency tracing, and validated remediation. - Layered Evidence Model: Orders evidence from provider service health down through resource state, change history, runtime signals, dependencies, and the user transaction path. - Safe Operational Actions: Guardrails for restarts, scaling, failover, certificate rotation, and redeployment, requiring blast-radius assessment, approval, rollback plans, and post-change verification. - Use Case: An Azure web app deployment reports success but users see errors. The Skill walks through runtime logs, DNS and certificate checks, and dependency health to find a stale secret reference, then guides a bounded secret rotation with consumer overlap validation. ## Quick Start Ask the assistant to investigate why your Azure application is failing after a recent deployment, providing the subscription, region, and resource ID.
