| name | chaos-impact |
| description | Synthesize an Azure Monitor impact report for a Chaos Studio v2 ScenarioRun: pulls the run, walks targeted resources, queries metrics/logs/activity-log/alerts over the run window ± buffer, and renders a Markdown + JSON impact card. |
ChaosImpact — Post-Run Azure Monitor Synthesis
⛔ ABSOLUTE RULE: Do NOT improvise, skip, or substitute any step. On ANY error, STOP and wait for the user.
When to use this skill (vs. the MCP server)
This skill is the human-interactive path: it resolves run context from the
shared startchaos-state.json, prompts for missing inputs via exit codes, and
renders a Markdown card plus a JSON sidecar. Use it when there is a user in the
loop — typically right after /start-chaos (or as a post-step of it).
If you are an autonomous agent with no user to prompt, call the three
Monitor tools on the chaos-studio MCP server directly (monitor_query_metrics,
monitor_query_logs, monitor_search_activity_log) and assemble your own
report. The PowerShell skill and the MCP tools are two independent surfaces
over the same Azure endpoints — neither calls the other.
Both surfaces target Microsoft.Chaos 2026-05-01-preview plus the pinned
Azure Monitor API versions in scripts/Constants.ps1, and use the local
az login session for auth.
How It Works
All synthesis logic lives in scripts/Invoke-ChaosImpact.ps1. The script
resolves the ScenarioRun, discovers Log Analytics workspaces via diagnostic
settings, runs the Monitor query fan-out, classifies signals, and writes both
artifacts.
The AI orchestrator's only job is:
- Set
$env:STARTCHAOS_STATE_PATH to
(the skill but does not this file).