[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BDKWYZC4DFX9YC08310S6":3,"skill-same:01M69BDKWYZC4DFX9YC08310S6":139},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M69BDKWYZC4DFX9YC08310S6","setup-scenario",null,"Discover recommended scenarios, build and validate a ScenarioConfiguration, and auto-fix resource permissions.","microsoft\u002Fchaos-studio","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BCX96C2ZS87TPZT4BZGP8",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fsetup-scenario\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26],"setup","setup scenario","validate","2026-11-10 10:12:30",false,"---\nname: setup-scenario\ndescription: \"Discover recommended scenarios, build and validate a ScenarioConfiguration, and auto-fix resource permissions.\"\n---\n\n# SetupScenario — Scenario Discovery, Configuration & Validation\n\n> ⛔ **ABSOLUTE RULE**: Do NOT improvise, skip, or substitute any step. On ANY error, STOP and wait for the user.\n\n## When to use this skill (vs. the MCP server)\n\nThis skill is the **human-interactive** path: it shares state with the rest of the pipeline, prompts via exit codes, and renders cards. Use it when there is a user in the loop.\n\nIf you are an **autonomous agent** with no user to prompt, use the MCP tools directly: `chaos_refresh_recommendations`, `chaos_list_recommended_scenarios`, `chaos_create_scenario_configuration`, `chaos_validate_scenario_configuration`, `chaos_fix_resource_permissions`. See `mcp\u002FREADME.md`.\n\nBoth surfaces target `Microsoft.Chaos` `2026-05-01-preview` and use the local `az login` session for auth.\n\n## How It Works\n\nAll discovery, configuration, validation, and permission-fix logic lives in `scripts\u002FInvoke-SetupScenario.ps1`. The script drives the Chaos Studio operations through the `az chaos` CLI extension — workspace evaluation, recommendation listing, scenario selection routing, parameter resolution, configuration creation, and the validate→fix→re-validate loop.\n\nThe AI orchestrator's **only** job is:\n\n1. Set `$env:STARTCHAOS_STATE_PATH` to `${SESSION_DIR}\u002Fstartchaos-state.json`.\n2. Run the script (no parameters needed for the first call).\n3. Handle exit codes that require user input (see below).\n4. Re-run the script with the user's answers as parameters.\n\n## Prerequisites\n\n- `state.workspace.status == \"done\"` (workspace must exist; the script refuses otherwise)\n- `state.context.subscriptionId` populated\n\n## Running the Script\n\n```powershell\n$env:STARTCHAOS_STATE_PATH = \"\u003Csession-dir>\u002Fstartchaos-state.json\"\n& \"\u003Cskill-dir>\u002Fscripts\u002FInvoke-SetupScenario.ps1\" @args\n```\n\nOn resume: re-runs short-circuit when `state.setup.status == \"done\"`.\n\n## Exit Codes → AI Actions\n\n| Exit | Meaning | AI Action |\n|------|---------|-----------|\n| **0** | Configuration created and validated | Done — summary already rendered by script. |\n| **1** | Hard error | STOP. Render the error from script output. Wait for user. State has `setup.lastError`. |\n| **2** | Scenario selection needed | Read `state.setup.recommendedScenarios` (or the script's rendered list). `ask_user` for one name. Re-run with `-ScenarioName \u003Cchosen>`. |\n| **3** | Parameter mode needed | Show the parameter table from the script output. `ask_user` which parameters they want to override (or accept defaults). Re-run with `-ParameterMode autofill` and `-ParameterValues @{ key = 'value' }` for any overrides. |\n\n### Important: Manual mode does NOT work\n\n`-ParameterMode manual` uses `Read-Host` prompts that do not render in a non-interactive AI session. **Always use `-ParameterMode autofill`** combined with `-ParameterValues` for any overrides the user requests.\n\n### Important: Exit 2 → 3 chaining\n\nWhen exit 2 is followed by exit 3 on re-run, combine both answers in the next invocation:\n```powershell\n& Invoke-SetupScenario.ps1 -ScenarioName \"ZoneDown-1.0\" -ParameterMode \"autofill\" -ParameterValues @{ duration = 'PT5M' }\n```\n\n## Script Parameters\n\n| Parameter | Description |\n|-----------|-------------|\n| `-ScenarioName` | Selected scenario (e.g. `ZoneDown-1.0`). Bypasses the selection prompt. Equivalent to `$env:STARTCHAOS_SCENARIO`. |\n| `-ParameterMode` | `autofill` (always use this — `manual` does not work in AI sessions). |\n| `-ParameterValues` | Hashtable of parameter overrides applied on top of defaults, e.g. `@{ duration = 'PT5M' }`. |\n\n## What the Script Handles (no AI logic needed)\n\n- Workspace evaluation via `az chaos workspace refresh-recommendation` (CLI awaits the LRO) + `show-evaluation` summary\n- Scenario list (`az chaos scenario list`) filtered to `recommendation.recommendationStatus == \"Recommended\"`\n- Auto-select when exactly one scenario is recommended; pause-and-emit-exit-2 otherwise\n- ScenarioConfiguration create (`az chaos scenario config create`, `--scenario-id` auto-derived) with parameter merge (defaults + overrides)\n- Validate (`az chaos scenario config validate`) → if not Succeeded → `az chaos scenario config fix-permissions` → re-validate\n- RBAC propagation retry loop (up to 5 minutes, 20s interval) gated to permission-related errors only\n- Atomic state writes with error envelopes\n- Idempotent re-runs\n\n## Related Skills\n\n- `create-workspace` — must complete before this skill\n- `run-scenario` — next phase after setup\n","# SetupScenario — Scenario Discovery, Configuration & Validation\n\n> ⛔ **ABSOLUTE RULE**: Do NOT improvise, skip, or substitute any step. On ANY error, STOP and wait for the user.\n\n## When to use this skill (vs. the MCP server)\n\nThis skill is the **human-interactive** path: it shares state with the rest of the pipeline, prompts via exit codes, and renders cards. Use it when there is a user in the loop.\n\nIf you are an **autonomous agent** with no user to prompt, use the MCP tools directly: `chaos_refresh_recommendations`, `chaos_list_recommended_scenarios`, `chaos_create_scenario_configuration`, `chaos_validate_scenario_configuration`, `chaos_fix_resource_permissions`. See `mcp\u002FREADME.md`.\n\nBoth surfaces target `Microsoft.Chaos` `2026-05-01-preview` and use the local `az login` session for auth.\n\n## How It Works\n\nAll discovery, configuration, validation, and permission-fix logic lives in `scripts\u002FInvoke-SetupScenario.ps1`. The script drives the Chaos Studio operations through the `az chaos` CLI extension — workspace evaluation, recommendation listing, scenario selection routing, parameter resolution, configuration creation, and the validate→fix→re-validate loop.\n\nThe AI orchestrator's **only** job is:\n\n1. Set `$env:STARTCHAOS_STATE_PATH` to `${SESSION_DIR}\u002Fstartchaos-state.json`.\n2. Run the script (no parameters needed for the first call).\n3. Handle exit codes that require user input (see below).\n4. Re-run the script with the user's answers as parameters.\n\n## Prerequisites\n\n- `state.workspace.status == \"done\"` (workspace must exist; the script refuses otherwise)\n- `state.context.subscriptionId` populated\n\n## Running the Script\n\n```powershell\n$env:STARTCHAOS_STATE_PATH = \"\u003Csession-dir>\u002Fstartchaos-state.json\"\n& \"\u003Cskill-dir>\u002Fscripts\u002FInvoke-SetupScenario.ps1\" @args\n```\n\nOn resume: re-runs short-circuit when `state.setup.status == \"done\"`.\n\n## Exit Codes → AI Actions\n\n| Exit | Meaning | AI Action |\n|------|---------|-----------|\n| **0** | Configuration created and validated | Done — summary already rendered by script. |\n| **1** | Hard error | STOP. Render the error from script output. Wait for user. State has `setup.lastError`. |\n| **2** | Scenario selection needed | Read `state.setup.recommendedScenarios` (or the script's rendered list). `ask_user` for one name. Re-run with `-ScenarioName \u003Cchosen>`. |\n| **3** | Parameter mode needed | Show the parameter table from the script output. `ask_user` which parameters they want to override (or accept defaults). Re-run with `-ParameterMode autofill` and `-ParameterValues @{ key = 'value' }` for any overrides. |\n\n### Important: Manual mode does NOT work\n\n`-ParameterMode manual` uses `Read-Host` prompts that do not render in a non-interactive AI session. **Always use `-ParameterMode autofill`** combined with `-ParameterValues` for any overrides the user requests.\n\n### Important: Exit 2 → 3 chaining\n\nWhen exit 2 is followed by exit 3 on re-run, combine both answers in the next invocation:\n```powershell\n& Invoke-SetupScenario.ps1 -ScenarioName \"ZoneDown-1.0\" -ParameterMode \"autofill\" -ParameterValues @{ duration = 'PT5M' }\n```\n\n## Script Parameters\n\n| Parameter | Description |\n|-----------|-------------|\n| `-ScenarioName` | Selected scenario (e.g. `ZoneDown-1.0`). Bypasses the selection prompt. Equivalent to `$env:STARTCHAOS_SCENARIO`. |\n| `-ParameterMode` | `autofill` (always use this — `manual` does not work in AI sessions). |\n| `-ParameterValues` | Hashtable of parameter overrides applied on top of defaults, e.g. `@{ duration = 'PT5M' }`. |\n\n## What the Script Handles (no AI logic needed)\n\n- Workspace evaluation via `az chaos workspace refresh-recommendation` (CLI awaits the LRO) + `show-evaluation` summary\n- Scenario list (`az chaos scenario list`) filtered to `recommendation.recommendationStatus == \"Recommended\"`\n- Auto-select when exactly one scenario is recommended; pause-and-emit-exit-2 otherwise\n- ScenarioConfiguration create (`az chaos scenario config create`, `--scenario-id` auto-derived) with parameter merge (defaults + overrides)\n- Validate (`az chaos scenario config validate`) → if not Succeeded → `az chaos scenario config fix-permissions` → re-validate\n- RBAC propagation retry loop (up to 5 minutes, 20s interval) gated to permission-related errors only\n- Atomic state writes with error envelopes\n- Idempotent re-runs\n\n## Related Skills\n\n- `create-workspace` — must complete before this skill\n- `run-scenario` — next phase after setup\n",{"name":5,"description":7},"main","6044a40e14cfafb6a7edb297a8a29e98cfe3c543","copilot-cli-plugin\u002Fskills\u002Fsetup-scenario",4,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-28 22:44:24",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add microsoft\u002Fchaos-studio --skill setup-scenario",{"tool":47,"command":48},"bunx","bunx skills add microsoft\u002Fchaos-studio --skill setup-scenario",{"tool":50,"command":51},"pnpm","pnpm dlx skills add microsoft\u002Fchaos-studio --skill setup-scenario","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fsetup-scenario\u002FSKILL.md",true,[55,61,65,69,73,77,81,85,89,93,97,101,105,109,113,117,123,127,131,135],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"prompts\u002Fanalyst-common.md","REFERENCE","参考文档",1582,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fanalyst-common.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"prompts\u002Fcost-and-time.md",1640,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fcost-and-time.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"prompts\u002Fplan-adherence.md",1637,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fplan-adherence.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"prompts\u002Fquality-evidence.md",1476,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fquality-evidence.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"prompts\u002Frepeated-work.md",1469,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Frepeated-work.md",{"path":78,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":79,"sourceHtmlUrl":80},"prompts\u002Frequest-conflicts.md",1011,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Frequest-conflicts.md",{"path":82,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":83,"sourceHtmlUrl":84},"prompts\u002Fscrub-audit.md",1363,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub-audit.md",{"path":86,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":87,"sourceHtmlUrl":88},"prompts\u002Fscrub.md",1471,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub.md",{"path":90,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":91,"sourceHtmlUrl":92},"prompts\u002Fsimilar-session.md",1711,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fsimilar-session.md",{"path":94,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":95,"sourceHtmlUrl":96},"prompts\u002Fskill-timeline.md",1646,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fskill-timeline.md",{"path":98,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":99,"sourceHtmlUrl":100},"prompts\u002Fstumbles.md",1330,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Fprompts\u002Fstumbles.md",{"path":102,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fcontext-safety.md",990,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Freferences\u002Fcontext-safety.md",{"path":106,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fgithub-issues.md",1644,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Freferences\u002Fgithub-issues.md",{"path":110,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fredaction-policy.md",2243,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Freferences\u002Fredaction-policy.md",{"path":114,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fsession-discovery.md",1859,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Freferences\u002Fsession-discovery.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002FInvoke-SetupScenario.ps1","SCRIPT","脚本",13079,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fsetup-scenario\u002Fscripts\u002FInvoke-SetupScenario.ps1",{"path":124,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":125,"sourceHtmlUrl":126},"templates\u002Fbundle-README.md",3672,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fbundle-README.md",{"path":128,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":129,"sourceHtmlUrl":130},"templates\u002Fcase.md",2983,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fcase.md",{"path":132,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":133,"sourceHtmlUrl":134},"templates\u002Fissue.md",1851,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fissue.md",{"path":136,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":137,"sourceHtmlUrl":138},"templates\u002Freport.md",2359,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fdiagnosing-superpowers\u002Ftemplates\u002Freport.md",[140,152,163,175,185,193],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":27},"01M69BDNKG9SA6RN6T9MA63EP8","start-chaos","Orchestrate the full Chaos Studio v2 workflow: auth → workspace → scenario → run. Shares a single state file and supports resume.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fstart-chaos\u002FSKILL.md",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148,149,150,151],"start chaos","run","auth","workflow",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":27},"01M69BDJ2ZYXPETM69X6SKP6YT","run-scenario","Execute a ScenarioConfiguration and stream ScenarioRun status with per-action breakdown until terminal state.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Frun-scenario\u002FSKILL.md",[158],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[160,149,161,162],"run scenario","status","terminal",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":27},"01M69BDGAJDDM8HM02YH8HSBDE","create-workspace","Provision a Microsoft.Chaos\u002Fworkspaces resource (v2), bind a managed identity, set scopes, and grant Reader RBAC on the scope.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fcreate-workspace\u002FSKILL.md",[169],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[171,172,173,174,9],"create workspace","create","identity","rbac",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":27},"01M69BDCS0CFAC1240TJKR91FY","chaos-study","Guided help for running a Chaos Studio study against an Azure workspace scope: frame a steady-state question with you, discover live which actions Chaos Studio offers for that region, freeze a plan, run a validated scenario configuration only with your explicit consent, collect the before\u002Fduring\u002Fafter signals you chose, and write a self-contained HTML report for your review. Start here for questions like 'what happens to my service when X?' or 'is my service resilient to X?'.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study\u002FSKILL.md",[],[182,149,183,184],"chaos study","azure","review",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":27},"01M69BDAY9AM9RXZKCW8653V5C","chaos-study-scope","Frame a Chaos study before anything runs: resolve or create a Chaos Studio V2 workspace, read the resources the service discovered inside its scopes, discover live which actions and scenarios are available for that region, express a falsifiable steady-state predicate, verify the action fits what is in scope, then freeze and hash the study plan.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-scope\u002FSKILL.md",[],[192,172],"chaos study scope",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":27},"01M69BD9106S43A040QY767T2B","chaos-study-run","Execute a frozen Chaos study plan against Azure using Chaos Studio V2: verify plan integrity, create and validate a scenario configuration, require an explicit typed consent phrase, collect baseline evidence, execute the scenario run, collect during and post-recovery evidence, and always clean up the configuration. Dry-run by default.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-run\u002FSKILL.md",[],[149,200,26,172,183],"chaos study run"]