[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBTGZHTZ7XG486M8M0X2PE":3,"skill-same:01M7CBTGZHTZ7XG486M8M0X2PE":55},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7CBTGZHTZ7XG486M8M0X2PE","chaos-engineer",null,"Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Fchaos-engineer\u002Fskills\u002Fchaos-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: chaos-engineer\ndescription: Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: devops\n  triggers: chaos engineering, resilience testing, failure injection, game day, blast radius, chaos experiment, fault injection, Chaos Monkey, Litmus Chaos, antifragile\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: sre-engineer, devops-engineer, kubernetes-specialist\n---\n\n# Chaos Engineer\n\n## When to Use This Skill\n\n- Designing and executing chaos experiments\n- Implementing failure injection frameworks (Chaos Monkey, Litmus, etc.)\n- Planning and conducting game day exercises\n- Building blast radius controls and safety mechanisms\n- Setting up continuous chaos testing in CI\u002FCD\n- Improving system resilience based on experiment findings\n\n## Core Workflow\n\n1. **System Analysis** - Map architecture, dependencies, critical paths, and failure modes\n2. **Experiment Design** - Define hypothesis, steady state, blast radius, and safety controls\n3. **Execute Chaos** - Run controlled experiments with monitoring and quick rollback\n4. **Learn & Improve** - Document findings, implement fixes, enhance monitoring\n5. **Automate** - Integrate chaos testing into CI\u002FCD for continuous resilience\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Experiments | `references\u002Fexperiment-design.md` | Designing hypothesis, blast radius, rollback |\n| Infrastructure | `references\u002Finfrastructure-chaos.md` | Server, network, zone, region failures |\n| Kubernetes | `references\u002Fkubernetes-chaos.md` | Pod, node, Litmus, chaos mesh experiments |\n| Tools & Automation | `references\u002Fchaos-tools.md` | Chaos Monkey, Gremlin, Pumba, CI\u002FCD integration |\n| Game Days | `references\u002Fgame-days.md` | Planning, executing, learning from game days |\n\n## Safety Checklist\n\nNon-obvious constraints that must be enforced on every experiment:\n\n- **Steady state first** — define and verify baseline metrics before injecting any failure\n- **Blast radius cap** — start with the smallest possible impact scope; expand only after validation\n- **Automated rollback ≤ 30 seconds** — abort path must be scripted and tested before the experiment begins\n- **Single variable** — change only one failure condition at a time until behaviour is well understood\n- **No production without safety nets** — customer-facing environments require circuit breakers, feature flags, or canary isolation\n- **Close the loop** — every experiment must produce a written learning summary and at least one tracked improvement\n\n## Output Templates\n\nWhen implementing chaos engineering, provide:\n1. Experiment design document (hypothesis, metrics, blast radius)\n2. Implementation code (failure injection scripts\u002Fmanifests)\n3. Monitoring setup and alert configuration\n4. Rollback procedures and safety controls\n5. Learning summary and improvement recommendations\n\n## Concrete Example: Pod Failure Experiment (Litmus Chaos)\n\nThe following shows a complete experiment — from hypothesis to rollback — using Litmus Chaos on Kubernetes.\n\n### Step 1 — Define steady state and apply the experiment\n\n```bash\n# Verify baseline: p99 latency \u003C 200ms, error rate \u003C 0.1%\nkubectl get deploy my-service -n production\nkubectl top pods -n production -l app=my-service\n```\n\n### Step 2 — Create and apply a Litmus ChaosEngine manifest\n\n```yaml\n# chaos-pod-delete.yaml\napiVersion: litmuschaos.io\u002Fv1alpha1\nkind: ChaosEngine\nmetadata:\n  name: my-service-pod-delete\n  namespace: production\nspec:\n  appinfo:\n    appns: production\n    applabel: \"app=my-service\"\n    appkind: deployment\n  # Limit blast radius: only 1 replica at a time\n  engineState: active\n  chaosServiceAccount: litmus-admin\n  experiments:\n    - name: pod-delete\n      spec:\n        components:\n          env:\n            - name: TOTAL_CHAOS_DURATION\n              value: \"60\"          # seconds\n            - name: CHAOS_INTERVAL\n              value: \"20\"          # delete one pod every 20s\n            - name: FORCE\n              value: \"false\"\n            - name: PODS_AFFECTED_PERC\n              value: \"33\"          # max 33% of replicas affected\n```\n\n```bash\n# Apply the experiment\nkubectl apply -f chaos-pod-delete.yaml\n\n# Watch experiment status\nkubectl describe chaosengine my-service-pod-delete -n production\nkubectl get chaosresult my-service-pod-delete-pod-delete -n production -w\n```\n\n### Step 3 — Monitor during the experiment\n\n```bash\n# Tail application logs for errors\nkubectl logs -l app=my-service -n production --since=2m -f\n\n# Check ChaosResult verdict when complete\nkubectl get chaosresult my-service-pod-delete-pod-delete \\\n  -n production -o jsonpath='{.status.experimentStatus.verdict}'\n```\n\n### Step 4 — Rollback \u002F abort if steady state is violated\n\n```bash\n# Immediately stop the experiment\nkubectl patch chaosengine my-service-pod-delete \\\n  -n production --type merge -p '{\"spec\":{\"engineState\":\"stop\"}}'\n\n# Confirm all pods are healthy\nkubectl rollout status deployment\u002Fmy-service -n production\n```\n\n## Concrete Example: Network Latency with toxiproxy\n\n```bash\n# Install toxiproxy CLI\nbrew install toxiproxy   # macOS; use the binary release on Linux\n\n# Start toxiproxy server (runs alongside your service)\ntoxiproxy-server &\n\n# Create a proxy for your downstream dependency\ntoxiproxy-cli create -l 0.0.0.0:22222 -u downstream-db:5432 db-proxy\n\n# Inject 300ms latency with 10% jitter — blast radius: this proxy only\ntoxiproxy-cli toxic add db-proxy -t latency -a latency=300 -a jitter=30\n\n# Run your load test \u002F observe metrics here ...\n\n# Remove the toxic to restore normal behaviour\ntoxiproxy-cli toxic remove db-proxy -n latency_downstream\n```\n\n## Concrete Example: Chaos Monkey (Spinnaker \u002F standalone)\n\n```bash\n# chaos-monkey-config.yml — restrict to a single ASG\ndeployment:\n  enabled: true\n  regionIndependence: false\nchaos:\n  enabled: true\n  meanTimeBetweenKillsInWorkDays: 2\n  minTimeBetweenKillsInWorkDays: 1\n  grouping: APP           # kill one instance per app, not per cluster\n  exceptions:\n    - account: production\n      region: us-east-1\n      detail: \"*-canary\"  # never kill canary instances\n\n# Apply and trigger a manual kill for testing\nchaos-monkey --app my-service --account staging --dry-run false\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fchaos-engineer\u002F)\n","# Chaos Engineer\n\n## When to Use This Skill\n\n- Designing and executing chaos experiments\n- Implementing failure injection frameworks (Chaos Monkey, Litmus, etc.)\n- Planning and conducting game day exercises\n- Building blast radius controls and safety mechanisms\n- Setting up continuous chaos testing in CI\u002FCD\n- Improving system resilience based on experiment findings\n\n## Core Workflow\n\n1. **System Analysis** - Map architecture, dependencies, critical paths, and failure modes\n2. **Experiment Design** - Define hypothesis, steady state, blast radius, and safety controls\n3. **Execute Chaos** - Run controlled experiments with monitoring and quick rollback\n4. **Learn & Improve** - Document findings, implement fixes, enhance monitoring\n5. **Automate** - Integrate chaos testing into CI\u002FCD for continuous resilience\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Experiments | `references\u002Fexperiment-design.md` | Designing hypothesis, blast radius, rollback |\n| Infrastructure | `references\u002Finfrastructure-chaos.md` | Server, network, zone, region failures |\n| Kubernetes | `references\u002Fkubernetes-chaos.md` | Pod, node, Litmus, chaos mesh experiments |\n| Tools & Automation | `references\u002Fchaos-tools.md` | Chaos Monkey, Gremlin, Pumba, CI\u002FCD integration |\n| Game Days | `references\u002Fgame-days.md` | Planning, executing, learning from game days |\n\n## Safety Checklist\n\nNon-obvious constraints that must be enforced on every experiment:\n\n- **Steady state first** — define and verify baseline metrics before injecting any failure\n- **Blast radius cap** — start with the smallest possible impact scope; expand only after validation\n- **Automated rollback ≤ 30 seconds** — abort path must be scripted and tested before the experiment begins\n- **Single variable** — change only one failure condition at a time until behaviour is well understood\n- **No production without safety nets** — customer-facing environments require circuit breakers, feature flags, or canary isolation\n- **Close the loop** — every experiment must produce a written learning summary and at least one tracked improvement\n\n## Output Templates\n\nWhen implementing chaos engineering, provide:\n1. Experiment design document (hypothesis, metrics, blast radius)\n2. Implementation code (failure injection scripts\u002Fmanifests)\n3. Monitoring setup and alert configuration\n4. Rollback procedures and safety controls\n5. Learning summary and improvement recommendations\n\n## Concrete Example: Pod Failure Experiment (Litmus Chaos)\n\nThe following shows a complete experiment — from hypothesis to rollback — using Litmus Chaos on Kubernetes.\n\n### Step 1 — Define steady state and apply the experiment\n\n```bash\n# Verify baseline: p99 latency \u003C 200ms, error rate \u003C 0.1%\nkubectl get deploy my-service -n production\nkubectl top pods -n production -l app=my-service\n```\n\n### Step 2 — Create and apply a Litmus ChaosEngine manifest\n\n```yaml\n# chaos-pod-delete.yaml\napiVersion: litmuschaos.io\u002Fv1alpha1\nkind: ChaosEngine\nmetadata:\n  name: my-service-pod-delete\n  namespace: production\nspec:\n  appinfo:\n    appns: production\n    applabel: \"app=my-service\"\n    appkind: deployment\n  # Limit blast radius: only 1 replica at a time\n  engineState: active\n  chaosServiceAccount: litmus-admin\n  experiments:\n    - name: pod-delete\n      spec:\n        components:\n          env:\n            - name: TOTAL_CHAOS_DURATION\n              value: \"60\"          # seconds\n            - name: CHAOS_INTERVAL\n              value: \"20\"          # delete one pod every 20s\n            - name: FORCE\n              value: \"false\"\n            - name: PODS_AFFECTED_PERC\n              value: \"33\"          # max 33% of replicas affected\n```\n\n```bash\n# Apply the experiment\nkubectl apply -f chaos-pod-delete.yaml\n\n# Watch experiment status\nkubectl describe chaosengine my-service-pod-delete -n production\nkubectl get chaosresult my-service-pod-delete-pod-delete -n production -w\n```\n\n### Step 3 — Monitor during the experiment\n\n```bash\n# Tail application logs for errors\nkubectl logs -l app=my-service -n production --since=2m -f\n\n# Check ChaosResult verdict when complete\nkubectl get chaosresult my-service-pod-delete-pod-delete \\\n  -n production -o jsonpath='{.status.experimentStatus.verdict}'\n```\n\n### Step 4 — Rollback \u002F abort if steady state is violated\n\n```bash\n# Immediately stop the experiment\nkubectl patch chaosengine my-service-pod-delete \\\n  -n production --type merge -p '{\"spec\":{\"engineState\":\"stop\"}}'\n\n# Confirm all pods are healthy\nkubectl rollout status deployment\u002Fmy-service -n production\n```\n\n## Concrete Example: Network Latency with toxiproxy\n\n```bash\n# Install toxiproxy CLI\nbrew install toxiproxy   # macOS; use the binary release on Linux\n\n# Start toxiproxy server (runs alongside your service)\ntoxiproxy-server &\n\n# Create a proxy for your downstream dependency\ntoxiproxy-cli create -l 0.0.0.0:22222 -u downstream-db:5432 db-proxy\n\n# Inject 300ms latency with 10% jitter — blast radius: this proxy only\ntoxiproxy-cli toxic add db-proxy -t latency -a latency=300 -a jitter=30\n\n# Run your load test \u002F observe metrics here ...\n\n# Remove the toxic to restore normal behaviour\ntoxiproxy-cli toxic remove db-proxy -n latency_downstream\n```\n\n## Concrete Example: Chaos Monkey (Spinnaker \u002F standalone)\n\n```bash\n# chaos-monkey-config.yml — restrict to a single ASG\ndeployment:\n  enabled: true\n  regionIndependence: false\nchaos:\n  enabled: true\n  meanTimeBetweenKillsInWorkDays: 2\n  minTimeBetweenKillsInWorkDays: 1\n  grouping: APP           # kill one instance per app, not per cluster\n  exceptions:\n    - account: production\n      region: us-east-1\n      detail: \"*-canary\"  # never kill canary instances\n\n# Apply and trigger a manual kill for testing\nchaos-monkey --app my-service --account staging --dry-run false\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fchaos-engineer\u002F)\n",{"name":5,"license":15,"metadata":24,"description":7},{"role":25,"scope":26,"author":27,"domain":28,"version":29,"triggers":30,"output-format":31,"related-skills":32},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","devops","1.1.0","chaos engineering, resilience testing, failure injection, game day, blast radius, chaos experiment, fault injection, Chaos Monkey, Litmus Chaos, antifragile","code","sre-engineer, devops-engineer, kubernetes-specialist","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjeffallan-claude-skills\u002Fchaos-engineer\u002Fskills\u002Fchaos-engineer",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill chaos-engineer",{"tool":47,"command":48},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill chaos-engineer",{"tool":50,"command":51},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill chaos-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Fchaos-engineer\u002Fskills\u002Fchaos-engineer\u002FSKILL.md",true,[],[56,63,68,75,80,87],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":64,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":76,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":88,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]