[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BD31GKTY3CAX6EBDBRSVQ":3,"skill-same:01M69BD31GKTY3CAX6EBDBRSVQ":97},{"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":28,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M69BD31GKTY3CAX6EBDBRSVQ","chaos-study-design",null,"Help decide what a Chaos study could test. Reads the system's code, deployment and telemetry first, then interviews the customer about what they want to learn, and only then suggests a ranked set of Chaos Studio V2 scenario candidates tied to the dependency edges it found. Writes a durable study brief that feeds chaos-study-scope without retyping.","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\u002Fchaos-study-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36],"design","chaos study design","customer","test","telemetry","deployment","learn","code","2026-11-10 10:12:30",false,"---\nname: chaos-study-design\ndescription: \"Help decide what a Chaos study could test. Reads the system's code, deployment and telemetry first, then interviews the customer about what they want to learn, and only then suggests a ranked set of Chaos Studio V2 scenario candidates tied to the dependency edges it found. Writes a durable study brief that feeds chaos-study-scope without retyping.\"\n---\n\n# chaos-study-design — what should we test, and why?\n\nStudies often go wrong before anything is injected. Someone picks a fault\nbecause it is available, runs it, sees nothing, and concludes the system is\nresilient. This skill tries to steer away from that outcome: it asks for the\nquestion *what would we learn?* to be answered — in the customer's own words and\nagainst the customer's own code — before a scenario is ever chosen.\n\n## Principles\n\n**Read before you ask.** Analysis always precedes the interview. Asking a\ncustomer \"what are your dependencies?\" when their repository is sitting right\nthere wastes their time and produces worse answers than reading it. Eight areas\nare inspected: code, deployment, dependencies, resilience behaviour, persistence,\nworkload, telemetry, and identity.\n\n**Unavailable is not unknown.** Each area is either *observed* with a citation —\na file, a symbol, a config key — or explicitly declared *unavailable* with a\nreason. Silence is rejected: `analyze` exits `24` and names every area left\nunaccounted for. A candidate hypothesis may never rest on evidence nobody read.\n\n**Grill, don't survey.** \"Test resilience\" is not a goal. Nine questions are\nasked one at a time, in dependency order, and vague answers are refused rather\nthan recorded. Four of them are *grounded*: the answer must engage with the\ncustomer's own system vocabulary — the services, dependencies and signals\nanalysis actually found — not generic reliability language.\n\n**Never ask what you already know.** A question that analysis already answered is\npre-filled and marked `establishedBy`. The customer is asked only for what only\nthey can supply: intent, business impact, risk appetite, abort criteria.\n\n**Candidates are code-grounded or they are not candidates.** Every candidate\ncarries eight mandatory fields — dependency edge, failure mechanism, mechanism\nevidence, mechanism probe, steady-state predicate, exposure inputs, collateral\nrisks, and abort criteria. A candidate missing any of them is rejected at\nconstruction, not at review.\n\n**The platform is asked, never assumed.** Candidates are intersected with live\nregional action discovery, workspace-discovered resources, and\nworkspace-recommended scenarios. When Azure cannot be reached, candidates are\nmarked `provisional`, limitation `L15` is recorded, and the brief says plainly\nthat platform availability is unconfirmed. No bundled catalogue, ever.\n\n**The customer chooses.** Two to four ranked candidates are presented with\nrationale and tradeoffs. Nothing is recommended as final until the customer\nreturns an exact confirmation phrase bound to the brief hash. On confirmation the\nbrief seals: the phrase keeps referring to what they actually saw.\n\n## Usage\n\nDesign is the first phase, and the front door drives it for you — that is the\nrecommended path, because it also enforces the ordering:\n\n```powershell\n..\u002Fchaos-study\u002Fscripts\u002FInvoke-ChaosStudy.ps1 -System \"orders-api\"\n```\n\nThe actions below are the same machine, exposed for expert use. Whichever route\nyou take, exit `26` means **the study is waiting on a person**: one question is\nopen. Ask the customer that single question with the host's interactive\nmechanism (`ask_user` where available), wait for their reply, pass it back with\n`-Answer`, and repeat. Never batch the questions into one message, never answer\non the customer's behalf, and never treat `26` as a failure.\n\n### 1. Start a brief\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action start -System \"orders-api\"\n```\n\nPrints a `briefId`. Every later action takes `-BriefId`.\n\n### 2. Record what you read\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action analyze -BriefId \u003Cid> `\n  -Observed 'code=src\u002FOrders\u002FPaymentGateway.cs:14 Charge() has no retry or timeout' `\n  -Observed 'dependencies=orders-api -> payments-api (synchronous, in request path)' `\n  -Observed 'telemetry=metrics:checkoutSuccessRate, metrics:paymentGatewayErrors' `\n  -Unavailable 'identity=no access to the subscription from this session'\n```\n\nRepeat `-Observed`\u002F`-Unavailable` per area. All eight must be accounted for.\n\n### 3. Propose candidates\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action candidates -BriefId \u003Cid> -CandidateFile .\u002Fcandidates.json\n```\n\nEach candidate needs the eight required fields. Ranking is computed:\navailability, then confidence, then evidence count, then whether exposure is\ncomputable. Pass `-Region`\u002F`-Workspace` to intersect with live discovery.\n\n### 4. Interview\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action interview -BriefId \u003Cid>\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action answer -BriefId \u003Cid> -QuestionId purpose -Answer \"...\"\n```\n\n`interview` prints the single next open question and exits `26`. The question is\nalso emitted between `CHAOS-QUESTION-BEGIN` \u002F `CHAOS-QUESTION-END` as JSON —\n`questionId`, `prompt`, `why`, `choices`, `grounded` — so an orchestrator can\nask exactly one question without parsing prose. When `choices` is present the\nanswer must be one of them verbatim. `answer` accepts or refuses; a refusal\nleaves the question open and exits `24` — it is not an error, it is the skill\ndoing its job.\n\n### 5. Recommend, then confirm\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action recommend -BriefId \u003Cid>\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action confirm -BriefId \u003Cid> `\n  -Select \u003CcandidateId> -ConfirmPhrase \"study \u003CcandidateId> on \u003Csystem> \u003Chash8>\"\n```\n\n`recommend` requires every question answered, and exits `26` because the choice\nis the customer's to make. `confirm` requires the exact case-sensitive phrase\nprinted by `recommend`.\n\n### 6. Hand off\n\n```powershell\n..\u002Fchaos-study-scope\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 -Brief \u003CbriefPath> -Workspace ... -ResourceGroup ...\n```\n\nScope reads the confirmed brief for hypothesis, steady state, failure mechanism,\nmechanism evidence, mechanism probe, exposure inputs, scenario parameters, blast\nradius and windows. Anything passed explicitly on the command line wins, so the\nbrief is a starting point rather than a cage.\n\n## Artifacts\n\nBriefs live at `\u003CstudyRoot>\u002Fbriefs\u002F\u003CbriefId>\u002Fstudy-brief.v1.json`, alongside but\nseparate from studies — a brief exists before there is a workspace to hash. The\nbrief carries `briefVersion`, `state`, the analysis with citations, candidates,\nthe interview transcript including refusals, the recommendation, the customer\nconfirmation, and `briefHash`.\n\nStates advance monotonically:\n`DRAFT → ANALYZED → CANDIDATES → INTERVIEWING → RECOMMENDED → CONFIRMED`.\nA confirmed brief is immutable; further writes exit `13`.\n\n## Exit codes\n\n| Code | Meaning |\n|------|---------|\n| `0`  | Success |\n| `1`  | Unexpected failure |\n| `13` | Brief already confirmed — start a new one |\n| `24` | Design incomplete — unaccounted area, vague answer, or missing field |\n| `26` | Awaiting customer input — a question is on the table. Not a failure. Ask it, then resume. |\n\n## What this skill does not do\n\nIt never contacts Azure to mutate anything, never creates a workspace, never\nvalidates a configuration and never injects a fault. It reads, asks, ranks and\nrecords. Everything with a blast radius belongs to `chaos-study-scope` and\n`chaos-study-run`, behind their own consent gates.\n","# chaos-study-design — what should we test, and why?\n\nStudies often go wrong before anything is injected. Someone picks a fault\nbecause it is available, runs it, sees nothing, and concludes the system is\nresilient. This skill tries to steer away from that outcome: it asks for the\nquestion *what would we learn?* to be answered — in the customer's own words and\nagainst the customer's own code — before a scenario is ever chosen.\n\n## Principles\n\n**Read before you ask.** Analysis always precedes the interview. Asking a\ncustomer \"what are your dependencies?\" when their repository is sitting right\nthere wastes their time and produces worse answers than reading it. Eight areas\nare inspected: code, deployment, dependencies, resilience behaviour, persistence,\nworkload, telemetry, and identity.\n\n**Unavailable is not unknown.** Each area is either *observed* with a citation —\na file, a symbol, a config key — or explicitly declared *unavailable* with a\nreason. Silence is rejected: `analyze` exits `24` and names every area left\nunaccounted for. A candidate hypothesis may never rest on evidence nobody read.\n\n**Grill, don't survey.** \"Test resilience\" is not a goal. Nine questions are\nasked one at a time, in dependency order, and vague answers are refused rather\nthan recorded. Four of them are *grounded*: the answer must engage with the\ncustomer's own system vocabulary — the services, dependencies and signals\nanalysis actually found — not generic reliability language.\n\n**Never ask what you already know.** A question that analysis already answered is\npre-filled and marked `establishedBy`. The customer is asked only for what only\nthey can supply: intent, business impact, risk appetite, abort criteria.\n\n**Candidates are code-grounded or they are not candidates.** Every candidate\ncarries eight mandatory fields — dependency edge, failure mechanism, mechanism\nevidence, mechanism probe, steady-state predicate, exposure inputs, collateral\nrisks, and abort criteria. A candidate missing any of them is rejected at\nconstruction, not at review.\n\n**The platform is asked, never assumed.** Candidates are intersected with live\nregional action discovery, workspace-discovered resources, and\nworkspace-recommended scenarios. When Azure cannot be reached, candidates are\nmarked `provisional`, limitation `L15` is recorded, and the brief says plainly\nthat platform availability is unconfirmed. No bundled catalogue, ever.\n\n**The customer chooses.** Two to four ranked candidates are presented with\nrationale and tradeoffs. Nothing is recommended as final until the customer\nreturns an exact confirmation phrase bound to the brief hash. On confirmation the\nbrief seals: the phrase keeps referring to what they actually saw.\n\n## Usage\n\nDesign is the first phase, and the front door drives it for you — that is the\nrecommended path, because it also enforces the ordering:\n\n```powershell\n..\u002Fchaos-study\u002Fscripts\u002FInvoke-ChaosStudy.ps1 -System \"orders-api\"\n```\n\nThe actions below are the same machine, exposed for expert use. Whichever route\nyou take, exit `26` means **the study is waiting on a person**: one question is\nopen. Ask the customer that single question with the host's interactive\nmechanism (`ask_user` where available), wait for their reply, pass it back with\n`-Answer`, and repeat. Never batch the questions into one message, never answer\non the customer's behalf, and never treat `26` as a failure.\n\n### 1. Start a brief\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action start -System \"orders-api\"\n```\n\nPrints a `briefId`. Every later action takes `-BriefId`.\n\n### 2. Record what you read\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action analyze -BriefId \u003Cid> `\n  -Observed 'code=src\u002FOrders\u002FPaymentGateway.cs:14 Charge() has no retry or timeout' `\n  -Observed 'dependencies=orders-api -> payments-api (synchronous, in request path)' `\n  -Observed 'telemetry=metrics:checkoutSuccessRate, metrics:paymentGatewayErrors' `\n  -Unavailable 'identity=no access to the subscription from this session'\n```\n\nRepeat `-Observed`\u002F`-Unavailable` per area. All eight must be accounted for.\n\n### 3. Propose candidates\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action candidates -BriefId \u003Cid> -CandidateFile .\u002Fcandidates.json\n```\n\nEach candidate needs the eight required fields. Ranking is computed:\navailability, then confidence, then evidence count, then whether exposure is\ncomputable. Pass `-Region`\u002F`-Workspace` to intersect with live discovery.\n\n### 4. Interview\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action interview -BriefId \u003Cid>\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action answer -BriefId \u003Cid> -QuestionId purpose -Answer \"...\"\n```\n\n`interview` prints the single next open question and exits `26`. The question is\nalso emitted between `CHAOS-QUESTION-BEGIN` \u002F `CHAOS-QUESTION-END` as JSON —\n`questionId`, `prompt`, `why`, `choices`, `grounded` — so an orchestrator can\nask exactly one question without parsing prose. When `choices` is present the\nanswer must be one of them verbatim. `answer` accepts or refuses; a refusal\nleaves the question open and exits `24` — it is not an error, it is the skill\ndoing its job.\n\n### 5. Recommend, then confirm\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action recommend -BriefId \u003Cid>\n.\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1 -Action confirm -BriefId \u003Cid> `\n  -Select \u003CcandidateId> -ConfirmPhrase \"study \u003CcandidateId> on \u003Csystem> \u003Chash8>\"\n```\n\n`recommend` requires every question answered, and exits `26` because the choice\nis the customer's to make. `confirm` requires the exact case-sensitive phrase\nprinted by `recommend`.\n\n### 6. Hand off\n\n```powershell\n..\u002Fchaos-study-scope\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 -Brief \u003CbriefPath> -Workspace ... -ResourceGroup ...\n```\n\nScope reads the confirmed brief for hypothesis, steady state, failure mechanism,\nmechanism evidence, mechanism probe, exposure inputs, scenario parameters, blast\nradius and windows. Anything passed explicitly on the command line wins, so the\nbrief is a starting point rather than a cage.\n\n## Artifacts\n\nBriefs live at `\u003CstudyRoot>\u002Fbriefs\u002F\u003CbriefId>\u002Fstudy-brief.v1.json`, alongside but\nseparate from studies — a brief exists before there is a workspace to hash. The\nbrief carries `briefVersion`, `state`, the analysis with citations, candidates,\nthe interview transcript including refusals, the recommendation, the customer\nconfirmation, and `briefHash`.\n\nStates advance monotonically:\n`DRAFT → ANALYZED → CANDIDATES → INTERVIEWING → RECOMMENDED → CONFIRMED`.\nA confirmed brief is immutable; further writes exit `13`.\n\n## Exit codes\n\n| Code | Meaning |\n|------|---------|\n| `0`  | Success |\n| `1`  | Unexpected failure |\n| `13` | Brief already confirmed — start a new one |\n| `24` | Design incomplete — unaccounted area, vague answer, or missing field |\n| `26` | Awaiting customer input — a question is on the table. Not a failure. Ask it, then resume. |\n\n## What this skill does not do\n\nIt never contacts Azure to mutate anything, never creates a workspace, never\nvalidates a configuration and never injects a fault. It reads, asks, ranks and\nrecords. Everything with a blast radius belongs to `chaos-study-scope` and\n`chaos-study-run`, behind their own consent gates.\n",{"name":5,"description":7},"main","6044a40e14cfafb6a7edb297a8a29e98cfe3c543","copilot-cli-plugin\u002Fskills\u002Fchaos-study-design",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add microsoft\u002Fchaos-studio --skill chaos-study-design",{"tool":57,"command":58},"bunx","bunx skills add microsoft\u002Fchaos-studio --skill chaos-study-design",{"tool":60,"command":61},"pnpm","pnpm dlx skills add microsoft\u002Fchaos-studio --skill chaos-study-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-design\u002FSKILL.md",true,[65,71,75,81,85,89,93],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"adopter-config.md","REFERENCE","参考文档",1823,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-pr-management\u002Fskills\u002Fstats\u002Fadopter-config.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"panels.md",3908,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-pr-management\u002Fskills\u002Fstats\u002Fpanels.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002FInvoke-ChaosStudyDesign.ps1","SCRIPT","脚本",40134,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-design\u002Fscripts\u002FInvoke-ChaosStudyDesign.ps1",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Flib\u002FBrief.ps1",11547,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-design\u002Fscripts\u002Flib\u002FBrief.ps1",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Flib\u002FCandidates.ps1",19538,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-design\u002Fscripts\u002Flib\u002FCandidates.ps1",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Flib\u002FInspect.ps1",10948,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-design\u002Fscripts\u002Flib\u002FInspect.ps1",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Flib\u002FInterview.ps1",18507,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-design\u002Fscripts\u002Flib\u002FInterview.ps1",[98,112,123,134,146,156],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":107,"publishedAt":37},"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",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[108,109,110,111],"start chaos","workflow","auth","run",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":37},"01M69BDKWYZC4DFX9YC08310S6","setup-scenario","Discover recommended scenarios, build and validate a ScenarioConfiguration, and auto-fix resource permissions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fsetup-scenario\u002FSKILL.md",[118],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122],"setup scenario","setup","validate",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":37},"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",[129],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[131,111,132,133],"run scenario","terminal","status",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":37},"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",[140],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[142,143,144,145,9],"create workspace","create","rbac","identity",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":37},"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",[],[153,111,154,155],"chaos study","azure","review",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":37},"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",[],[163,143],"chaos study scope"]