Skip to content
Development
Skill

/azure-chaos-studio

Expert knowledge for Chaos Studio development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when automating Chaos Studio via CLI/ARM/REST, configuring AKS agents, Private

From plugin
azure-agent-skills
811200 skills

Claude Code

$ npx -y skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio --agent claude-code

SKILL.md

azure-chaos-studio.SKILL.md
name: azure-chaos-studio
description: Expert knowledge for Chaos Studio development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when automating Chaos Studio via CLI/ARM/REST, configuring AKS agents, Private Link, CMK, or migrating to Workspaces, and other Chaos Studio related development tasks. Not for Azure Monitor (use azure-monitor), Azure Resiliency (use azure-resiliency), Azure Reliability (use azure-reliability), Azure Defender For Cloud (use azure-defender-for-cloud).
compatibility: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
metadata:
  generated_at: "2026-11-01"
  generator: "docs2skills/1.0.0"

Chaos Studio Skill

This skill provides expert guidance for Chaos Studio. Covers troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.

How to Use This Skill

> **IMPORTANT for Agent**: Use the **Category Index** below to locate relevant sections. For categories with line ranges (e.g., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file

> **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md)

This skill requires **network access** to fetch documentation content:

  • **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown.
  • **Fallback**: Use `fetch_webpage` with query string `from=learn-agent-skill&accept=text/markdown`. Returns Markdown.

Category Index

| Category | Lines | Description | |----------|-------|-------------| | Troubleshooting | L36-L44 | Diagnosing and fixing Chaos Studio agent, workspace, scenario, and classic experiment issues, including status verification, known errors, and common deployment/runtime failures. | | Best Practices | L45-L50 | Guidance on designing Chaos Studio scenarios to test AKS node resilience and on filtering/targeting specific Azure resources when configuring chaos experiments. | | Decision Making | L51-L56 | Guidance on when to use Chaos Workspaces vs classic Experiments and how to migrate existing Chaos Studio classic experiments into Workspaces. | | Limits & Quotas | L57-L63 | Limits, quotas, and known issues for Chaos Studio classic and Workspaces preview, including experiment constraints, feature gaps, and current platform limitations. | | Security | L64-L77 | Networking, identity, RBAC, and encryption setup for Chaos Studio/AKS: agent connectivity, IP allowlists, Private Link, workspace roles, least-privilege access, and customer-managed keys. | | Configuration | L78-L91 | Configuring Chaos Studio experiments: workspaces, scenarios, targets (static/dynamic), virtual network injection, Azure Policy, and using fault/action libraries and templates. | | Integrations & Coding Patterns | L92-L113 | Patterns and examples for automating, integrating, and scripting Chaos Studio experiments and agents using CLI, ARM/Bicep, REST, Logic Apps, and Azure monitoring/telemetry tools. | | Deployment | L114-L121 | Checking OS/region/model compatibility, and deploying Chaos Studio classic experiments and targets using ARM templates, including version and fault support details. |

Troubleshooting

| Topic | URL | |-------|-----| | Resolve known Chaos Studio agent issues | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-agent-known-issues | | Troubleshoot Azure Chaos Studio agent issues | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-agent-troubleshooting | | Verify and diagnose Chaos Studio agent status | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-agent-verify-status | | Troubleshoot Chaos Studio Workspaces and scenarios | https://learn.microsoft.com/en-us/azure/chaos-studio/troubleshoot-workspaces-scenarios | | Troubleshoot Azure Chaos Studio classic experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/troubleshooting |

Best Practices

| Topic | URL | |-------|-----| | Test AKS node resilience with Chaos Studio Workspaces | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-aks-guidance | | Filter and target resources in Chaos Studio Scenarios | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-workspaces-resource-targeting |

Decision Making

| Topic | URL | |-------|-----| | Migrate from Chaos Studio classic experiments to Workspaces | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-migrate-from-classic | | Choose between Chaos Workspaces and Experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-workspaces-vs-experiments |

Limits & Quotas

| Topic | URL | |-------|-----| | Review limitations and known issues for Chaos Experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-limitations | | Review Chaos Studio classic service limits and quotas | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-service-limits | | Review Chaos Studio Workspaces preview limitations | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-workspaces-limitations |

Security

| Topic | URL | |-------|-----| | Understand Chaos Studio agent networking and identity | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-agent-concepts | | Configure AKS authentication for Chaos Experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-aks-authentication | | Prepare AKS clusters and permi

Read more
@microsoftdocs
Ships withazure-agent-skills

๐Ÿš€ Agentic Skills for Azure Development Supercharge your AI coding assistant with curated, production-ready skills for Microsoft Azure.

Stars on GitHub

Momentum

stars in total
811
Star history of MicrosoftDocs/Agent-Skills on GitHub, a chart by star-history.com

Other skills on azure-agent-skills.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, orโ€ฆ

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android โ€” semantic ARIA roles and labels,โ€ฆ

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commitsโ€ฆ

react2d252k
@facebook@facebookInstall Skill

Questions about azure-chaos-studio.

Which coding agents can use azure-chaos-studio?
azure-chaos-studio installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.