chaos-impact Skill
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. Published by microsoft in chaos-studio.
What is chaos-impact Skill?
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. Published by microsoft in chaos-studio. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use chaos-impact Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/chaos-studio
- Skill file: copilot-cli-plugin/skills/chaos-impact/SKILL.md
What it does
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.
Skill instructions
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 (monitorquerymetrics, monitorquerylogs, monitorsearchactivitylog) 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 sess
Explore related resources
Frequently asked questions
What is chaos-impact?
chaos-impact is a open-source AI agent skill with Copy skill directory. 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.
Who is chaos-impact best for?
chaos-impact is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install chaos-impact?
Install or run chaos-impact using Copy skill directory. Check chaos-impact for the latest setup command.
Is chaos-impact actively maintained?
chaos-impact may need a closer maintenance check before production use.
Auto-fetched from GitHub.
