Azure Diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.
Expert knowledge for Chaos Studio development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment.
Install Azure Chaos Studio
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-chaos-studio --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/azure-chaos-studio .claude/skills/azure-chaos-studio && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azure-chaos-studio" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-chaos-studio into .claude/skills/azure-chaos-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-chaos-studio", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-chaos-studioType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-chaos-studio --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/azure-chaos-studio .agents/skills/azure-chaos-studio && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azure-chaos-studio" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-chaos-studio into .agents/skills/azure-chaos-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-chaos-studio", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-chaos-studio --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/azure-chaos-studio .cursor/skills/azure-chaos-studio && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azure-chaos-studio" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-chaos-studio into .cursor/skills/azure-chaos-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-chaos-studio", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MicrosoftDocs/Agent-Skills.git --path skills/azure-chaos-studio--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-chaos-studio --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/azure-chaos-studio .gemini/skills/azure-chaos-studio && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azure-chaos-studio" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-chaos-studio into .gemini/skills/azure-chaos-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-chaos-studio", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MicrosoftDocs/Agent-Skills azure-chaos-studioInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/azure-chaos-studio .github/skills/azure-chaos-studio && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azure-chaos-studio" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-chaos-studio into .github/skills/azure-chaos-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-chaos-studio", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-chaos-studio --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/azure-chaos-studio .opencode/skills/azure-chaos-studio && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azure-chaos-studio" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-chaos-studio into .opencode/skills/azure-chaos-studio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-chaos-studio", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azure-chaos-studio- GitHub stars
- 777
- Token cost
- ~3k tokens
- SKILL.md length
- 816 words
- Files
- 1
- Skills in repo
- 149
- Repo updated
- First seen
- Licence
- CC-BY-4.0
At a glance
Expert knowledge for Chaos Studio development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment.
- Automating Chaos Studio via CLI/ARM
- SKILL.md covers How to Use This Skill and Category Index
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Configuring faults/targets
What it does
Azure Chaos Studio is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. 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, configuring faults/targets, securing networks/identity, or choosing Workspaces vs classic, and other Chaos Studio related development tasks. Not for Azure Resiliency (use azure-resiliency), Azure Reliability (use azure-reliability), Azure Monitor (use azure-monitor), Azure…
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires network access. Uses mcpmicrosoftdocs:microsoftdocsfetch or fetchwebpage to retrieve documentation.
It sits in DevOps & Cloud. It works with Microsoft Azure and Azure Monitor. The repository describes itself as: Curated Agent Skills for Microsoft & Azure – giving AI coding assistants structured, real-time expertise from Microsoft Learn docs. The licence is CC-BY-4.0.
When your agent uses it
- Automating Chaos Studio via CLI/ARM
- Configuring faults/targets
- Securing networks/identity
- Choosing Workspaces vs classic
Example prompts
- “/azure-chaos-studio”
Requirements
- Compatibility (from SKILL.md): Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
What it can do on your machine
Read from SKILL.md and the folder at commit ba74e8f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
learn.microsoft.comgithub.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
From compatibility in the SKILL.md frontmatter.
Context cost
Azure Chaos Studio loads about 3k tokens when it runs. Until then it costs about 144 tokens; SKILL.md has 816 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from MicrosoftDocs/Agent-Skills at commit ba74e8f, republished under its CC-BY-4.0 licence (© MicrosoftDocs). 816 words, ~2,957 tokens.
Download SKILL.mdSave it as
.claude/skills/azure-chaos-studio/SKILL.md (or your agent's skills folder).- 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, configuring faults/targets, securing networks/identity, or choosing Workspaces vs classic, and other Chaos Studio related development tasks. Not for Azure Resiliency (use azure-resiliency), Azure Reliability (use azure-reliability), Azure Monitor (use azure-monitor), Azure Site Recovery (use azure-site-recovery).
- compatibility
- Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
- metadata.generated_at
- 2026-10-04
- metadata.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), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
- Preferred: Use
mcp_microsoftdocs:microsoft_docs_fetchwith query stringfrom=learn-agent-skill. Returns Markdown. - Fallback: Use
fetch_webpagewith query stringfrom=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-L49 | Known issues, limitations, and workarounds for the Chaos Studio agent, plus guidance for using Chaos Studio Workspaces to test AKS node zone resilience and failure scenarios. |
| Decision Making | L50-L55 | Guidance on when to use Chaos Workspaces vs classic Experiments and how to migrate existing classic experiments into Workspaces. |
| Limits & Quotas | L56-L62 | Limits, quotas, and known issues for Chaos Studio classic, experiments, and Workspaces preview, including feature restrictions and current platform limitations. |
| Security | L63-L76 | Networking, identity, RBAC, AKS auth, IP allowlists, Private Link, CMK, and least-privilege role design for securely running Chaos Studio experiments and workspaces. |
| Configuration | L77-L87 | Configuring and managing Chaos Studio classic experiments, including faults/actions, target selection (static/dynamic), virtual network injection, and Azure Policy-based target configuration. |
| Integrations & Coding Patterns | L88-L111 | 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 | L112-L119 | 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 zone resilience with Chaos Studio Workspaces | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-aks-guidance |
Decision Making
| Topic | URL |
|---|---|
| Migrate from 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
Show full SKILL.md (293 more words)Show less
Configuration
| Topic | URL |
|---|---|
| Use Chaos Studio fault and action library | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-fault-library |
| Set up virtual network injection for Chaos Studio | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-private-networking |
| Run and manage classic Chaos Studio experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-run-experiment |
| Configure target selection for classic experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-target-selection |
| Configure targets and capabilities for classic experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-targets-capabilities |
| Configure dynamic targets in portal for classic experiments | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-tutorial-dynamic-target-portal |
| Configure Chaos Studio classic targets via Azure Policy | https://learn.microsoft.com/en-us/azure/chaos-studio/sample-policy-targets |
Integrations & Coding Patterns
Deployment
| Topic | URL |
|---|---|
| Check OS and fault support for Chaos Studio agent | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-agent-os-support |
| Check regional availability for Chaos Studio models | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-region-availability |
| Check Chaos Studio classic version compatibility | https://learn.microsoft.com/en-us/azure/chaos-studio/chaos-studio-versions |
| Deploy classic experiments with ARM template samples | https://learn.microsoft.com/en-us/azure/chaos-studio/sample-template-experiment |
| Deploy Chaos Studio targets via ARM templates | https://learn.microsoft.com/en-us/azure/chaos-studio/sample-template-targets |
© MicrosoftDocs, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/azure-chaos-studio of MicrosoftDocs/Agent-Skills.
Open the folder on GitHubat commit ba74e8f
Compare with similar skills
Azure Chaos Studio next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azure Chaos Studio this skillMicrosoftDocs/Agent-Skills | 777 | — | ~3k | Automated safety check: Pass | CC-BY-4.0 | |
| Azure Diagnosticsmicrosoft/azure-skills | 1.5k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Azure Monitor Ingestion Javamicrosoft/skills | 3.1k | 6 repos | ~2k | Automated safety check: Pass | MIT | |
| Azure Monitor Ingestion Pymicrosoft/skills | 3.1k | 6 repos | ~2k | Automated safety check: Pass | MIT | |
| Azure Monitor Opentelemetry Exporter Javamicrosoft/skills | 3.1k | 6 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Azure Monitor Opentelemetry Exporter Pymicrosoft/skills | 3.1k | 6 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Azure Monitor Ingestion Java
microsoft/skills
Azure Monitor Ingestion SDK for Java. An agent skill from microsoft/skills.
- Official
Azure Monitor Ingestion Py
microsoft/skills
Azure Monitor Ingestion SDK for Python. An agent skill from microsoft/skills.
- Official
Azure Monitor Opentelemetry Exporter Java
microsoft/skills
Azure Monitor OpenTelemetry Exporter for Java. An agent skill from microsoft/skills.
- Official
Azure Monitor Opentelemetry Exporter Py
microsoft/skills
Azure Monitor OpenTelemetry Exporter for Python. An agent skill from microsoft/skills.
- Official
Azure Monitor Opentelemetry Py
microsoft/skills
Azure Monitor OpenTelemetry Distro for Python. An agent skill from microsoft/skills.
More from MicrosoftDocs/Agent-Skills
All 149 skills in this repo- Official
Azure Personalizer
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Personalizer development including troubleshooting, decision making, security, configuration, and integrations & coding patterns.
- Official
Azure Architecture Advisor
MicrosoftDocs/Agent-Skills
Guides Azure solution design by category, from reference architectures and design patterns to technology choices and migrations, fetching current Microsoft Learn pages over the network.
- Official
Azure Advisor Guidance
MicrosoftDocs/Agent-Skills
Reference guidance for Azure Advisor work: recommendations, alerts and digests, workbooks, RBAC access and sovereign-cloud limits, fetched from Microsoft Learn.
- Official
Azure AI Vision Reference
MicrosoftDocs/Agent-Skills
Looks up Microsoft Learn guidance for Azure AI Vision: Image Analysis, Read OCR containers, smart-crop thumbnails, background removal and video frame analysis, plus limits and deployment.
- Official
Azure Analysis Services
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Analysis Services development including troubleshooting.
- Official
Azure Anomaly Detector
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Anomaly Detector development including troubleshooting, best practices, limits & quotas, configuration, and deployment.
Related
Works with
Categories
Questions about Azure Chaos Studio
What does Azure Chaos Studio do?
Expert knowledge for Chaos Studio development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Azure Chaos Studio is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. Expert knowledge for Chaos Studio development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment.
When should I use Azure Chaos Studio?
Azure Chaos Studio fits situations like: automating Chaos Studio via CLI/ARM; configuring faults/targets; securing networks/identity; choosing Workspaces vs classic.
How do I install Azure Chaos Studio in Claude Code?
Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a claude-code`. Or copy the skill folder (skills/azure-chaos-studio in MicrosoftDocs/Agent-Skills) into .claude/skills/azure-chaos-studio in your project. Claude Code loads it when a task matches its description.
How do I install Azure Chaos Studio in Codex?
Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a codex`. Or copy the skill folder (skills/azure-chaos-studio in MicrosoftDocs/Agent-Skills) into .agents/skills/azure-chaos-studio in your project. Codex loads it when a task matches its description.
Can I use Azure Chaos Studio in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-chaos-studio -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-chaos-studio, .gemini/skills/azure-chaos-studio, .github/skills/azure-chaos-studio and .opencode/skills/azure-chaos-studio in your project.
What does Azure Chaos Studio need to run?
SKILL.md names no scripts, command-line tools or credentials: Azure Chaos Studio is instructions for the agent only. Compatibility (from SKILL.md): Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation..
Does Azure Chaos Studio access the network?
SKILL.md names 2 domains. As links in the text: learn.microsoft.com and github.com. This is read from the text; nothing was executed.
Is Azure Chaos Studio safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Azure Chaos Studio use?
Azure Chaos Studio is published under the CC-BY-4.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azure Chaos Studio use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Azure Chaos Studio?
Skills that share tags, products or a category with Azure Chaos Studio: Azure Diagnostics (microsoft/azure-skills, 1.5k stars), Azure Monitor Ingestion Java (microsoft/skills, 3.1k stars), Azure Monitor Ingestion Py (microsoft/skills, 3.1k stars) and Azure Monitor Opentelemetry Exporter Java (microsoft/skills, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azure Chaos Studio?
MicrosoftDocs (a GitHub organization, an official publisher) maintains it in MicrosoftDocs/Agent-Skills, which has 777 GitHub stars. The repository holds 149 skills in this directory. The repository was last updated on October 5, 2026.
Source: MicrosoftDocs/Agent-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.