[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BDAY9AM9RXZKCW8653V5C":3,"skill-same:01M69BDAY9AM9RXZKCW8653V5C":105},{"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":18,"publishedAt":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M69BDAY9AM9RXZKCW8653V5C","chaos-study-scope",null,"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.","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-scope\u002FSKILL.md",[],[19,20],"chaos study scope","create","2026-11-10 10:12:30",false,"---\nname: chaos-study-scope\ndescription: \"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.\"\n---\n\n# chaos-study-scope — decide what the study can test\n\nChaos studies often go wrong here, not during execution. They run an action\nnothing was measuring, over a scope that could not receive it, to answer a\nquestion that could not have come back false.\n\nThis skill's job is to catch that before any resource is touched.\n\n## Principles\n\n**The workspace is the lifecycle root.** Scopes, discovered resources,\nscenarios, configurations and runs all hang off one workspace. Scoping resolves\nit first, and everything the plan records is anchored to it.\n\n**Ask the platform; never assume.** The list of available actions is fetched\nfrom `Microsoft.Chaos\u002Flocations\u002F{region}\u002Factions` for the workspace's region, on\nevery scope. That response is authoritative: its `canonicalId`, `actionType`,\n`appliesTo` and `parametersSchema` are what the plan records. Scenarios come\nfrom the workspace's own recommendation list.\n\n**No bundled catalogue, no fallback.** This skill ships no action definitions.\nIf the actions endpoint cannot be reached — not logged in, no permission, region\nunresolved — scoping stops with exit `16` and says so. It does not degrade to a\nstale local list, because a stale list is how you plan a study against an action\nthat does not exist.\n\n**What is in scope is read, not asserted.** The resources a run will touch come\nfrom the workspace's discovered resources, not from the operator's mental model.\nThe two diverge constantly — a scope grows a resource nobody remembered, or a\nresource the plan names was never onboarded and would have been silently\nskipped.\n\n**A steady state must be falsifiable.** `successRate >= 99.5` can be violated.\n\"the service is healthy\" cannot. Scoping rejects the second kind.\n\n**Check the fit before promising the study.** An empty scope, or an action that\napplies to no resource type present in the scope, means the study cannot prove\nanything. Scoping says so up front (exit `10` \u002F `14`) instead of failing halfway\nthrough a run.\n\n**Parameters are validated against the service's schema.** Not against a copy of\nit. Required properties, enums and types come from the live `parametersSchema`,\nso validation cannot drift from the platform. Scenario knobs and action knobs\nare different documents: `-Parameters` is checked against the scenario's schema\nand is what the configuration carries, `-ActionParameters` against the action's.\nNeither is ever silently checked against the other.\n\n**Freeze what was approved.** The plan is written once and hashed. The run skill\nre-computes that hash; if it changed, the run refuses (exit `12`). What you\nreviewed is what executes.\n\n**Discovery is read-only.** Scoping issues only reads, unless you explicitly ask\nfor `-CreateWorkspace`. Nothing else here mutates anything.\n\n## Usage\n\n**List what the platform offers** — start here; the action constrains the\nquestion, and only the service knows what exists in that region today:\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 -ListActions `\n    -SubscriptionId $sub -ResourceGroup rg-prod -WorkspaceName ws-payments\n\n.\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 -ListScenarios `\n    -SubscriptionId $sub -ResourceGroup rg-prod -WorkspaceName ws-payments\n```\n\n**Scope a study:**\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 `\n    -SubscriptionId $sub -ResourceGroup rg-prod -WorkspaceName ws-payments `\n    -Scenario '\u003Cscenario from -ListScenarios>' `\n    -Action '\u003Caction from -ListActions>' `\n    -SteadyState 'successRate >= 99.5' `\n    -SignalSource 'metrics:Availability' `\n    -DurationMinutes 10 -BaselineMinutes 5 -RecoveryMinutes 10\n```\n\n`-Action` accepts the canonical URN, the action name or the display name; a\npartial match is accepted only when it is unambiguous.\n\nUseful switches:\n\n- `-CreateWorkspace -Scope \u003CarmId...>` — create the workspace over those scopes\n  when it does not exist. Without it, a missing workspace is an error rather\n  than an implicit provisioning action.\n- `-Location` — region for a workspace being created\n- `-Parameters @{ ... }` — scenario knobs, validated against the live scenario\n  schema; these are what the configuration carries\n- `-ActionParameters @{ ... }` — action knobs, validated against the action's own\n  schema and recorded on the plan. The V2 configuration body takes scenario\n  parameters only, so these are declared and frozen, never transmitted.\n- `-FilterLocation` \u002F `-FilterZone` \u002F `-ExcludeResource` \u002F `-ExcludeType` \u002F\n  `-ExcludeTag` — the blast radius, frozen onto the plan as the configuration's\n  `filters` and `exclusions`. **A declared filter is not verified discovery\n  metadata.** Discovery does not report a location or zone, so resources missing\n  those attributes are retained as candidates with the attribute unverified, the\n  uncertainty is printed, and the declared filter is still transmitted for the\n  service to enforce. The preview cannot narrow what it cannot see, and it must\n  not widen what you asked for either.\n- `-SignalSource` — the evidence to collect (`metrics:` \u002F `logs:`); no defaults\n  are invented for you\n- `-Hypothesis` — what you expect to happen, recorded for honesty at report time\n- `-SkipDiscovery` — plan without contacting Azure. The plan then carries\n  limitation `L10` and records the scenario and action as `unverified-offline`;\n  no metadata is fabricated, and the run still validates before executing.\n\nOutput is a frozen `study-plan.v3.json` plus a study id. Nothing is executed.\n\n## What the plan records\n\nThe plan is the contract the rest of the suite reads:\n\n| Section | Why it matters |\n| --- | --- |\n| `workspace` | the lifecycle root — subscription, group, name, id, region, scopes |\n| `scope` | what is actually in scope: discovered resources, types, blast radius, and how many survive it |\n| `action` | live action metadata: canonical id, type, what it applies to, schema, roles |\n| `scenario` | the scenario that will execute, its version and parameters |\n| `discovery` | which endpoint answered, when, and how much it returned |\n| `question` | the steady-state predicate, parsed and normalised |\n| `windows` | baseline \u002F inject \u002F recovery minutes |\n| `signals` | what evidence must be collected for the verdict to mean anything |\n| `readiness` | gate results and any limitation codes they imply |\n| `planHash` | integrity seal checked before execution |\n\n## Choosing windows\n\nBaseline exists to establish what \"normal\" looked like *today*, not last week.\nRecovery exists to distinguish a transient dip from real damage — without it, a\nsystem that never recovers looks identical to one that recovers instantly.\n\nInjection windows of three minutes or less are recorded as limitation `L7`: too\nshort to distinguish resilience from luck.\n\n## Progressive discovery\n\nAction identifiers, parameter shapes and required permissions are **not**\ndocumented here. They are the service's to state, and restating them locally is\nexactly the drift this design removes. Use `-ListActions` and `-ListScenarios`.\n\nWhat lives locally is the method:\n\n- `..\u002Fchaos-study\u002Freferences\u002Fstudy-method.md` — the method behind the phases\n- `..\u002Fchaos-study\u002Freferences\u002Freport-contract.md` — what a report may claim\n\n## Exit codes\n\n| Code | Meaning |\n| --- | --- |\n| `0` | Plan frozen |\n| `1` | Error |\n| `10` | Readiness gates failed |\n| `14` | Scope unverified — nothing in scope, or the action does not fit it |\n| `16` | Live action discovery unavailable — there is no fallback |\n| `18` | Paused: an Azure operation must be executed by the host, then resumed |\n| `19` | Paused: role assignments need their own, separate approval |\n| `20` | Scenario would run fewer legs than it declares, and that was not accepted |\n| `21` | The run would not exercise the failure often enough to mean anything |\n| `22` | No adapter can reach Azure — pass `-Adapter` explicitly |\n| `23` | Study was written by an older contract version |\n\n### The pauses\n\n`18`, `19`, `20` and `21` are stops with a specific missing input, not errors.\nSupply it and re-run the same command; scoping resumes rather than restarting.\n\n- **`18`** — under `-Adapter external` this phase cannot call Azure itself. It\n  wrote the exact request to the study's `operations\u002F` directory. Execute it with\n  your own authenticated tooling, write the response back as the matching result\n  file, then re-run. Never answer the request from memory or inference: the\n  result is hashed and bound to the request, and invented evidence cannot seal.\n- **`19`** — preflight validation found the workspace identity is missing role\n  assignments. Granting them is a *separate* decision from approving the fault,\n  so it needs its own approval phrase. Approving the injection never implies it.\n- **`20`** — the service's execution plan skips legs the scenario name implies.\n  Fix the scope, or accept the reduced scenario explicitly.\n- **`21`** — the exposure arithmetic says the fault would rarely meet the code\n  path. Strengthen the exercise, or accept a weak one explicitly and let the\n  study report \"Not exercised\" rather than false resilience.\n\n## Next\n\nReview the plan, then run it with explicit consent:\n\n```powershell\nchaos-study-run -StudyId \u003CstudyId> -DryRun:$false -Consent '\u003Cphrase from the plan>'\n```\n","# chaos-study-scope — decide what the study can test\n\nChaos studies often go wrong here, not during execution. They run an action\nnothing was measuring, over a scope that could not receive it, to answer a\nquestion that could not have come back false.\n\nThis skill's job is to catch that before any resource is touched.\n\n## Principles\n\n**The workspace is the lifecycle root.** Scopes, discovered resources,\nscenarios, configurations and runs all hang off one workspace. Scoping resolves\nit first, and everything the plan records is anchored to it.\n\n**Ask the platform; never assume.** The list of available actions is fetched\nfrom `Microsoft.Chaos\u002Flocations\u002F{region}\u002Factions` for the workspace's region, on\nevery scope. That response is authoritative: its `canonicalId`, `actionType`,\n`appliesTo` and `parametersSchema` are what the plan records. Scenarios come\nfrom the workspace's own recommendation list.\n\n**No bundled catalogue, no fallback.** This skill ships no action definitions.\nIf the actions endpoint cannot be reached — not logged in, no permission, region\nunresolved — scoping stops with exit `16` and says so. It does not degrade to a\nstale local list, because a stale list is how you plan a study against an action\nthat does not exist.\n\n**What is in scope is read, not asserted.** The resources a run will touch come\nfrom the workspace's discovered resources, not from the operator's mental model.\nThe two diverge constantly — a scope grows a resource nobody remembered, or a\nresource the plan names was never onboarded and would have been silently\nskipped.\n\n**A steady state must be falsifiable.** `successRate >= 99.5` can be violated.\n\"the service is healthy\" cannot. Scoping rejects the second kind.\n\n**Check the fit before promising the study.** An empty scope, or an action that\napplies to no resource type present in the scope, means the study cannot prove\nanything. Scoping says so up front (exit `10` \u002F `14`) instead of failing halfway\nthrough a run.\n\n**Parameters are validated against the service's schema.** Not against a copy of\nit. Required properties, enums and types come from the live `parametersSchema`,\nso validation cannot drift from the platform. Scenario knobs and action knobs\nare different documents: `-Parameters` is checked against the scenario's schema\nand is what the configuration carries, `-ActionParameters` against the action's.\nNeither is ever silently checked against the other.\n\n**Freeze what was approved.** The plan is written once and hashed. The run skill\nre-computes that hash; if it changed, the run refuses (exit `12`). What you\nreviewed is what executes.\n\n**Discovery is read-only.** Scoping issues only reads, unless you explicitly ask\nfor `-CreateWorkspace`. Nothing else here mutates anything.\n\n## Usage\n\n**List what the platform offers** — start here; the action constrains the\nquestion, and only the service knows what exists in that region today:\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 -ListActions `\n    -SubscriptionId $sub -ResourceGroup rg-prod -WorkspaceName ws-payments\n\n.\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 -ListScenarios `\n    -SubscriptionId $sub -ResourceGroup rg-prod -WorkspaceName ws-payments\n```\n\n**Scope a study:**\n\n```powershell\n.\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1 `\n    -SubscriptionId $sub -ResourceGroup rg-prod -WorkspaceName ws-payments `\n    -Scenario '\u003Cscenario from -ListScenarios>' `\n    -Action '\u003Caction from -ListActions>' `\n    -SteadyState 'successRate >= 99.5' `\n    -SignalSource 'metrics:Availability' `\n    -DurationMinutes 10 -BaselineMinutes 5 -RecoveryMinutes 10\n```\n\n`-Action` accepts the canonical URN, the action name or the display name; a\npartial match is accepted only when it is unambiguous.\n\nUseful switches:\n\n- `-CreateWorkspace -Scope \u003CarmId...>` — create the workspace over those scopes\n  when it does not exist. Without it, a missing workspace is an error rather\n  than an implicit provisioning action.\n- `-Location` — region for a workspace being created\n- `-Parameters @{ ... }` — scenario knobs, validated against the live scenario\n  schema; these are what the configuration carries\n- `-ActionParameters @{ ... }` — action knobs, validated against the action's own\n  schema and recorded on the plan. The V2 configuration body takes scenario\n  parameters only, so these are declared and frozen, never transmitted.\n- `-FilterLocation` \u002F `-FilterZone` \u002F `-ExcludeResource` \u002F `-ExcludeType` \u002F\n  `-ExcludeTag` — the blast radius, frozen onto the plan as the configuration's\n  `filters` and `exclusions`. **A declared filter is not verified discovery\n  metadata.** Discovery does not report a location or zone, so resources missing\n  those attributes are retained as candidates with the attribute unverified, the\n  uncertainty is printed, and the declared filter is still transmitted for the\n  service to enforce. The preview cannot narrow what it cannot see, and it must\n  not widen what you asked for either.\n- `-SignalSource` — the evidence to collect (`metrics:` \u002F `logs:`); no defaults\n  are invented for you\n- `-Hypothesis` — what you expect to happen, recorded for honesty at report time\n- `-SkipDiscovery` — plan without contacting Azure. The plan then carries\n  limitation `L10` and records the scenario and action as `unverified-offline`;\n  no metadata is fabricated, and the run still validates before executing.\n\nOutput is a frozen `study-plan.v3.json` plus a study id. Nothing is executed.\n\n## What the plan records\n\nThe plan is the contract the rest of the suite reads:\n\n| Section | Why it matters |\n| --- | --- |\n| `workspace` | the lifecycle root — subscription, group, name, id, region, scopes |\n| `scope` | what is actually in scope: discovered resources, types, blast radius, and how many survive it |\n| `action` | live action metadata: canonical id, type, what it applies to, schema, roles |\n| `scenario` | the scenario that will execute, its version and parameters |\n| `discovery` | which endpoint answered, when, and how much it returned |\n| `question` | the steady-state predicate, parsed and normalised |\n| `windows` | baseline \u002F inject \u002F recovery minutes |\n| `signals` | what evidence must be collected for the verdict to mean anything |\n| `readiness` | gate results and any limitation codes they imply |\n| `planHash` | integrity seal checked before execution |\n\n## Choosing windows\n\nBaseline exists to establish what \"normal\" looked like *today*, not last week.\nRecovery exists to distinguish a transient dip from real damage — without it, a\nsystem that never recovers looks identical to one that recovers instantly.\n\nInjection windows of three minutes or less are recorded as limitation `L7`: too\nshort to distinguish resilience from luck.\n\n## Progressive discovery\n\nAction identifiers, parameter shapes and required permissions are **not**\ndocumented here. They are the service's to state, and restating them locally is\nexactly the drift this design removes. Use `-ListActions` and `-ListScenarios`.\n\nWhat lives locally is the method:\n\n- `..\u002Fchaos-study\u002Freferences\u002Fstudy-method.md` — the method behind the phases\n- `..\u002Fchaos-study\u002Freferences\u002Freport-contract.md` — what a report may claim\n\n## Exit codes\n\n| Code | Meaning |\n| --- | --- |\n| `0` | Plan frozen |\n| `1` | Error |\n| `10` | Readiness gates failed |\n| `14` | Scope unverified — nothing in scope, or the action does not fit it |\n| `16` | Live action discovery unavailable — there is no fallback |\n| `18` | Paused: an Azure operation must be executed by the host, then resumed |\n| `19` | Paused: role assignments need their own, separate approval |\n| `20` | Scenario would run fewer legs than it declares, and that was not accepted |\n| `21` | The run would not exercise the failure often enough to mean anything |\n| `22` | No adapter can reach Azure — pass `-Adapter` explicitly |\n| `23` | Study was written by an older contract version |\n\n### The pauses\n\n`18`, `19`, `20` and `21` are stops with a specific missing input, not errors.\nSupply it and re-run the same command; scoping resumes rather than restarting.\n\n- **`18`** — under `-Adapter external` this phase cannot call Azure itself. It\n  wrote the exact request to the study's `operations\u002F` directory. Execute it with\n  your own authenticated tooling, write the response back as the matching result\n  file, then re-run. Never answer the request from memory or inference: the\n  result is hashed and bound to the request, and invented evidence cannot seal.\n- **`19`** — preflight validation found the workspace identity is missing role\n  assignments. Granting them is a *separate* decision from approving the fault,\n  so it needs its own approval phrase. Approving the injection never implies it.\n- **`20`** — the service's execution plan skips legs the scenario name implies.\n  Fix the scope, or accept the reduced scenario explicitly.\n- **`21`** — the exposure arithmetic says the fault would rarely meet the code\n  path. Strengthen the exercise, or accept a weak one explicitly and let the\n  study report \"Not exercised\" rather than false resilience.\n\n## Next\n\nReview the plan, then run it with explicit consent:\n\n```powershell\nchaos-study-run -StudyId \u003CstudyId> -DryRun:$false -Consent '\u003Cphrase from the plan>'\n```\n",{"name":5,"description":7},"main","6044a40e14cfafb6a7edb297a8a29e98cfe3c543","copilot-cli-plugin\u002Fskills\u002Fchaos-study-scope",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add microsoft\u002Fchaos-studio --skill chaos-study-scope",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002Fchaos-studio --skill chaos-study-scope",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002Fchaos-studio --skill chaos-study-scope","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-scope\u002FSKILL.md",true,[49,55,59,63,67,71,75,79,83,89,93,97,101],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"audit-log-pr.md","REFERENCE","参考文档",7093,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Faudit-log-pr.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"audit-record-schema.md",3751,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Faudit-record-schema.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"gather.md",3204,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Fgather.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"outcomes\u002Finjection.md",938,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Foutcomes\u002Finjection.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"outcomes\u002Fredacted.md",712,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Foutcomes\u002Fredacted.md",{"path":72,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":73,"sourceHtmlUrl":74},"outcomes\u002Fschema-violations.md",687,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Foutcomes\u002Fschema-violations.md",{"path":76,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":77,"sourceHtmlUrl":78},"prerequisites.md",806,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Fprerequisites.md",{"path":80,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":81,"sourceHtmlUrl":82},"references.md",1436,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmagpie\u002Fblob\u002Fmain\u002Fplugins\u002Fmagpie-release-management\u002Fskills\u002Faudit-report\u002Freferences.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002FInvoke-ChaosStudyScope.ps1","SCRIPT","脚本",62912,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-scope\u002Fscripts\u002FInvoke-ChaosStudyScope.ps1",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Flib\u002FActionDiscovery.ps1",16010,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-scope\u002Fscripts\u002Flib\u002FActionDiscovery.ps1",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Flib\u002FBriefHandoff.ps1",16726,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-scope\u002Fscripts\u002Flib\u002FBriefHandoff.ps1",{"path":98,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Flib\u002FReadiness.ps1",58928,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-scope\u002Fscripts\u002Flib\u002FReadiness.ps1",{"path":102,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Flib\u002FWorkspace.ps1",41753,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fchaos-studio\u002Fblob\u002Fmain\u002Fcopilot-cli-plugin\u002Fskills\u002Fchaos-study-scope\u002Fscripts\u002Flib\u002FWorkspace.ps1",[106,122,133,144,155,165],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":117,"publishedAt":21},"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",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[118,119,120,121],"start chaos","run","auth","workflow",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":21},"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",[128],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[130,131,132],"setup scenario","setup","validate",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":21},"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",[139],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[141,119,142,143],"run scenario","status","terminal",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":21},"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",[150],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[20,152,153,154,9],"create workspace","rbac","identity",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":21},"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",[],[162,163,119,164],"chaos study","review","azure",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":21},"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",[],[119,172,164,20,132],"chaos study run"]