{"slug":"circuit-breaker-testing","title":"circuit-breaker-testing","summary":"Use this skill when you need evidence-bounded circuit-breaker-testing analysis and validation preparation; triggers include 熔断器测试 and circuit-breaker-testing.","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-24T14:54:59.974123Z","repo":{"url":"https://github.com/naodeng/awesome-qa-skills","stars":230,"forks":31,"license":null,"updatedAt":"2026-09-22T13:51:34Z"},"bodyHtml":"<hr>\n<h2>name: circuit-breaker-testing\ndescription: Use this skill when you need evidence-bounded circuit-breaker-testing analysis and validation preparation; triggers include 熔断器测试 and circuit-breaker-testing.</h2>\n<h1>Circuit-Breaker Testing</h1>\n<h2>When to Use</h2>\n<ul>\n<li>Use this Skill when the work needs evidence-bounded analysis of closed, open, and half-open states, threshold evidence, recovery probes, and fallback.</li>\n<li>Use it when the input is incomplete but a reviewable first draft with assumptions and gaps is still useful.</li>\n<li>Use it when static design evidence must remain separate from planned validation and completed execution.</li>\n</ul>\n<h2>Output Format Options</h2>\n<ul>\n<li>Default to Markdown organized by risk, evidence, and priority.</li>\n<li>If the user asks for a table, CSV, JSON, or ticket format, preserve the same finding fields and evidence states.</li>\n<li>Confirm the schema, enum values, and required fields before feeding the output to automation.</li>\n</ul>\n<h2>How to Use</h2>\n<ol>\n<li>Read prompts/circuit-breaker-testing.md and follow its input audit, coverage checklist, and output order.</li>\n<li>Extract scope, environment, version, dependencies, constraints, success criteria, and available evidence.</li>\n<li>Model closed, open, and half-open states, threshold evidence, recovery probes, and fallback with scenarios and decision criteria, prioritizing high-impact or hard-to-detect items.</li>\n<li>Separate facts, evidence-backed inferences, candidate recommendations, and Human decisions.</li>\n<li>When information is missing, deliver a bounded draft and the smallest evidence-gathering actions; do not write recommendations as execution results.</li>\n</ol>\n<h2>Reference Files</h2>\n<ul>\n<li>Read prompts/circuit-breaker-testing.md for every invocation; it is the complete execution contract.</li>\n<li>Read evals/eval.yaml and the matching evals/cases/ when evaluating the Skill.</li>\n<li>Read references/, examples/, scripts/, or output-formats.md only when the directory exists and the task needs it.</li>\n</ul>\n<h2>Core Constraints</h2>\n<ul>\n<li>Analyze only closed, open, and half-open states, threshold evidence, recovery probes, and fallback; do not inject faults, access real dependencies, or call production systems.</li>\n<li>Do not invent thresholds, availability, recovery times, vulnerability states, or completed test runs.</li>\n<li>Mark unsupported claims as pending, blocked, or unassessed and provide a validation method.</li>\n<li>Leave risk acceptance, release approval, and Human takeover to a Human.</li>\n</ul>\n<h2>Delivery Self-Check</h2>\n<ul>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Complete the six-part input audit and mark evidence freshness.</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Cover the circuit-breaker state, failure modes, expected concerns, and validation method.</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Separate facts, inferences, recommendations, gaps, and Human decisions.</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Do not turn static design or a dry-run into a claim of execution, passing, or release.</li>\n</ul>\n<h2>Common Pitfalls</h2>\n<ul>\n<li>Treating adjacent performance, incident, or API analysis as a complete substitute for Circuit-Breaker Testing.</li>\n<li>Listing steps without triggers, expected results, owner roles, or close conditions.</li>\n<li>Refusing incomplete input, or filling critical facts with template assumptions.</li>\n</ul>\n<h2>Best Practices</h2>\n<ul>\n<li>Start with the paths most likely to cause business loss or recovery failure.</li>\n<li>Use the smallest isolated and reversible validation suggestion, with explicit stop conditions.</li>\n<li>Make every conclusion reviewable by another engineer from its evidence and boundary.</li>\n</ul>\n","files":[{"path":"agents/openai.yaml","sizeBytes":336,"isText":true},{"path":"evals/cases/basic-success.yaml","sizeBytes":1416,"isText":true},{"path":"evals/cases/edge-incomplete-input.yaml","sizeBytes":856,"isText":true},{"path":"evals/cases/edge-scope-boundary.yaml","sizeBytes":971,"isText":true},{"path":"evals/eval.yaml","sizeBytes":441,"isText":true},{"path":"evals/local-rules.json","sizeBytes":142,"isText":true},{"path":"evals/trigger-prompts.csv","sizeBytes":472,"isText":false},{"path":"prompts/circuit-breaker-testing.md","sizeBytes":4045,"isText":true},{"path":"SKILL.md","sizeBytes":3339,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-24T14:57:29.195189Z","sha256":"C031BE9361720F78F171BE95DA93EA2DFF2BFCC98288ABCB0D2B2EC5D298098E","sizeBytes":6492},"review":null,"source":{"repositoryUrl":"https://github.com/naodeng/awesome-qa-skills","path":"skills/en/testing-types/circuit-breaker-testing","license":null,"commit":"c44b8922085e01bafc804d1ffa3f21d4cec1d1c5","subtreeSha":"04E32C6407717DCC9362B8DC0FD81A57435C812D23BD94B8FA632D4748AF6B00","lastSyncedAt":"2026-09-24T14:54:50.849933Z"},"reviewedAt":"2026-09-24T15:05:58.565066Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/circuit-breaker-testing"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart"},{"target":"git","command":"git clone https://github.com/naodeng/awesome-qa-skills.git"}]}