- Home
- Skills
- Agents & Orchestration
- Repair Circuit Breaker & Fallback Logic
More screenshots
Works with the AI Agents you already use
Repair Circuit Breaker & Fallback Logic
Diagnose and repair circuit breakers, failure classification, open/half-open transitions, probes, fallbacks, and recovery behavior.
$1
Repair Circuit Breaker & Fallback Logic
Example session with this skill installed
Our payment gateway breaker isn't opening when Stripe returns 401s, but it does for 503s. Here is the Resilience4j config and the log snippet showing the leaked 401 errors.
- Read your context and instructions
- Compiled the repair circuit breaker
The diagnosis indicates that 401 Unauthorized is being treated as a business logic error rather than a system failure, excluding it from the failure rate calculation. This prevents the breaker from opening even when the credential rotation fails globally.
Circuit Breaker Repair
| Component | Current State | Proposed Change | Reason |
|---|---|---|---|
| Failure Classification | recordExceptions: [IOException.class] | Add NotAuthorizedException.class | 401s in this context indicate a systemic auth failure. |
| Sliding Window | COUNT_BASED (100) | TIME_BASED (30s) | Low volume auth calls take too long to hit count thresholds. |
| Transition Logic | Manual reset only | waitDurationInOpenState: 10s | Allow automatic recovery attempts after cooldown. |
Implementation Patch (Resilience4j YAML)
resilience4j.circuitbreaker:
instances:
paymentGateway:
slidingWindowType: TIME_BASED
slidingWindowSize: 30
minimumNumberOfCalls: 5
failureRateThreshold: 50
waitDurationInOpenState: 10s
recordExceptions:
- java.io.IOException
- com.payment.exception.NotAuthorizedException
ignoreExceptions:
- com.payment.exception.InvalidCardException
Next steps
- Update the
recordExceptionslist in your application configuration. - Run the provided deterministic test case using a
TestTimeSourceto verify the transition to OPEN after 5 failed auth attempts. - Monitor the
resilience4j_circuitbreaker_statemetric during the next deployment.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair Circuit Breaker & Fallback Logic is a bounded ToolForge Labs workflow. Diagnose and repair circuit breakers, failure classification, open/half-open transitions, probes, fallbacks, and recovery behavior. Works from full repositories or partial context such as snippets, logs, configuration, traces, and architecture notes. Produces concrete repairs or evidence-backed review outputs while preserving existing product/security policy.
It works from a full repository or partial evidence such as snippets, logs, configuration, traces, tickets, and architecture notes. The skill preserves existing product and security policy, separates verified facts from assumptions, avoids invented execution claims, and produces concrete repair or review steps with focused deterministic validation or traceable evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Cannot verify production systems, external services, or facts that are not present in supplied evidence. With partial context it returns bounded diagnosis/review, explicit assumptions, and a deterministic validation plan rather than claiming successful execution.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
Use a clean branch or a controlled review workspace. Supply repository files, logs, traces, configuration, or evidence needed for the task. Review all patches/findings before merge or operational action; keep production credentials and destructive production actions out of the workflow.