Claude Skill

chaos-testing

Use this skill when you need evidence-bounded chaos-testing analysis and validation preparation; triggers include 混沌测试 and chaos-testing.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download naodeng-awesome-qa-skills-skills_en_testing-types_chaos-testing-9df700b.zip · 8 KB

Install

skills CLI npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/chaos-testing
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
Git git clone https://github.com/naodeng/awesome-qa-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Chaos Testing

When to Use

  • Use this Skill when the work needs evidence-bounded analysis of fault-injection hypotheses, blast radius, stop conditions, and safety guardrails.
  • Use it when the input is incomplete but a reviewable first draft with assumptions and gaps is still useful.
  • Use it when static design evidence must remain separate from planned validation and completed execution.

Output Format Options

  • Default to Markdown organized by risk, evidence, and priority.
  • If the user asks for a table, CSV, JSON, or ticket format, preserve the same finding fields and evidence states.
  • Confirm the schema, enum values, and required fields before feeding the output to automation.

How to Use

  1. Read prompts/chaos-testing.md and follow its input audit, coverage checklist, and output order.
  2. Extract scope, environment, version, dependencies, constraints, success criteria, and available evidence.
  3. Model fault-injection hypotheses, blast radius, stop conditions, and safety guardrails with scenarios and decision criteria, prioritizing high-impact or hard-to-detect items.
  4. Separate facts, evidence-backed inferences, candidate recommendations, and Human decisions.
  5. When information is missing, deliver a bounded draft and the smallest evidence-gathering actions; do not write recommendations as execution results.

Reference Files

  • Read prompts/chaos-testing.md for every invocation; it is the complete execution contract.
  • Read evals/eval.yaml and the matching evals/cases/ when evaluating the Skill.
  • Read references/, examples/, scripts/, or output-formats.md only when the directory exists and the task needs it.

Domain Execution Essentials

  • Express steady-state hypotheses as metrics, windows, baseline/control groups and business invariants; state the disruption's proposed causal chain.
  • Deliver hypothesis/control/injection/blast-radius/stop/rollback/evidence cards; name readiness blockers explicitly and never treat a design as a passed experiment.
  • When deriving domain candidates, read and follow prompts/chaos-testing.md for the domain procedure and oracle; retain valid controls, evidence gaps, and validation actions for each item.

Core Constraints

  • Analyze only fault-injection hypotheses, blast radius, stop conditions, and safety guardrails; do not inject faults, access real dependencies, or call production systems.
  • Do not invent thresholds, availability, recovery times, vulnerability states, or completed test runs.
  • Mark unsupported claims as pending, blocked, or unassessed and provide a validation method.
  • Leave risk acceptance, release approval, and Human takeover to a Human.

Delivery Self-Check

  • Complete the six-part input audit and mark evidence freshness.
  • Cover the fault-injection hypothesis, failure modes, expected concerns, and validation method.
  • Separate facts, inferences, recommendations, gaps, and Human decisions.
  • Do not turn static design or a dry-run into a claim of execution, passing, or release.

Common Pitfalls

  • Treating adjacent performance, incident, or API analysis as a complete substitute for Chaos Testing.
  • Listing steps without triggers, expected results, owner roles, or close conditions.
  • Refusing incomplete input, or filling critical facts with template assumptions.

Best Practices

  • Start with the paths most likely to cause business loss or recovery failure.
  • Use the smallest isolated and reversible validation suggestion, with explicit stop conditions.
  • Make every conclusion reviewable by another engineer from its evidence and boundary.
Files (awesome-qa-skills)
  • agents
    • openai.yaml 296 B
      Loading…
  • evals
    • cases
      • basic-success.yaml 1.4 KB
        Loading…
      • domain-method-control.yaml 1.2 KB
        Loading…
      • domain-method-success.yaml 1.3 KB
        Loading…
      • edge-incomplete-input.yaml 841 B
        Loading…
      • edge-scope-boundary.yaml 971 B
        Loading…
    • eval.yaml 531 B
      Loading…
    • local-rules.json 132 B
      Loading…
    • trigger-prompts.csv 467 B · in bundle
  • prompts
    • chaos-testing.md 5 KB
      Loading…
  • SKILL.md 4 KB
    ---
    name: chaos-testing
    description: Use this skill when you need evidence-bounded chaos-testing analysis and validation preparation; triggers include 混沌测试 and chaos-testing.
    license: PolyForm-Noncommercial-1.0.0
    metadata:
      version: "1.0.0"
      compatibility: ""
      author: "Awesome QA Skills contributors"
      language: "en"
      category: "testing-types"
      source: "https://github.com/naodeng/awesome-qa-skills"
      license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
    ---
    
    # Chaos Testing
    
    ## When to Use
    
    - Use this Skill when the work needs evidence-bounded analysis of fault-injection hypotheses, blast radius, stop conditions, and safety guardrails.
    - Use it when the input is incomplete but a reviewable first draft with assumptions and gaps is still useful.
    - Use it when static design evidence must remain separate from planned validation and completed execution.
    
    ## Output Format Options
    
    - Default to Markdown organized by risk, evidence, and priority.
    - If the user asks for a table, CSV, JSON, or ticket format, preserve the same finding fields and evidence states.
    - Confirm the schema, enum values, and required fields before feeding the output to automation.
    
    ## How to Use
    
    1. Read prompts/chaos-testing.md and follow its input audit, coverage checklist, and output order.
    2. Extract scope, environment, version, dependencies, constraints, success criteria, and available evidence.
    3. Model fault-injection hypotheses, blast radius, stop conditions, and safety guardrails with scenarios and decision criteria, prioritizing high-impact or hard-to-detect items.
    4. Separate facts, evidence-backed inferences, candidate recommendations, and Human decisions.
    5. When information is missing, deliver a bounded draft and the smallest evidence-gathering actions; do not write recommendations as execution results.
    
    ## Reference Files
    
    - Read prompts/chaos-testing.md for every invocation; it is the complete execution contract.
    - Read evals/eval.yaml and the matching evals/cases/ when evaluating the Skill.
    - Read references/, examples/, scripts/, or output-formats.md only when the directory exists and the task needs it.
    
    ## Domain Execution Essentials
    
    - Express steady-state hypotheses as metrics, windows, baseline/control groups and business invariants; state the disruption's proposed causal chain.
    - Deliver hypothesis/control/injection/blast-radius/stop/rollback/evidence cards; name readiness blockers explicitly and never treat a design as a passed experiment.
    - When deriving domain candidates, read and follow [prompts/chaos-testing.md](prompts/chaos-testing.md) for the domain procedure and oracle; retain valid controls, evidence gaps, and validation actions for each item.
    
    ## Core Constraints
    
    - Analyze only fault-injection hypotheses, blast radius, stop conditions, and safety guardrails; do not inject faults, access real dependencies, or call production systems.
    - Do not invent thresholds, availability, recovery times, vulnerability states, or completed test runs.
    - Mark unsupported claims as pending, blocked, or unassessed and provide a validation method.
    - Leave risk acceptance, release approval, and Human takeover to a Human.
    
    ## Delivery Self-Check
    
    - [ ] Complete the six-part input audit and mark evidence freshness.
    - [ ] Cover the fault-injection hypothesis, failure modes, expected concerns, and validation method.
    - [ ] Separate facts, inferences, recommendations, gaps, and Human decisions.
    - [ ] Do not turn static design or a dry-run into a claim of execution, passing, or release.
    
    ## Common Pitfalls
    
    - Treating adjacent performance, incident, or API analysis as a complete substitute for Chaos Testing.
    - Listing steps without triggers, expected results, owner roles, or close conditions.
    - Refusing incomplete input, or filling critical facts with template assumptions.
    
    ## Best Practices
    
    - Start with the paths most likely to cause business loss or recovery failure.
    - Use the smallest isolated and reversible validation suggestion, with explicit stop conditions.
    - Make every conclusion reviewable by another engineer from its evidence and boundary.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.