Individual skill
resilience-circuit-breaker-designer
Designs circuit breakers, bulkhead concurrency limits, fallback caches, and timeout policies for failing dependencies.
skills/development/resilience-circuit-breaker-designer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 630 bytesSKILL.mdcore · 1,832 bytesexamples/example.mddoc · 1,069 bytes
Read excerpt
## Purpose
Protect applications from cascading failures when downstream dependencies (third-party APIs, microservices, databases) become slow or unresponsive, using Circuit Breakers, Bulkheads, Timeouts, and Graceful Fallbacks.
## When to Use
- Calling third-party APIs (Stripe, Twilio, OpenAI, shipment tracking) that occasionally degrade.
- Preventing thread/connection exhaustion when one downstream microservice stalls.
- Implementing graceful degradation (e.g. returning cached recommendations when AI engine is down).
## What to Analyze
1. **Circuit States**: `CLOSED` (normal), `OPEN` (failing fast without calling downstream), `HALF-OPEN` (probing recovery).
2. **Threshold Metrics**: Failure percentage threshold (e.g. >50% errors over 20 requests) and slow call duration threshold.