SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.3.0 · Reviewed 2026-08-02

Circuit Breaker Tuning Advisor

Reduce production risk in threshold selection and window sizing with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Tunes thresholds, windows, and half-open probing so breakers protect without tripping on noise.

₹299 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Threshold selection
  • Window sizing
  • Half-open behavior

How Circuit Breaker Tuning Advisor works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind threshold selection

It decides

A window sizing plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Circuit Breaker Tuning Advisor tunes thresholds, windows, and half-open probing so breakers protect without tripping on noise. Use it when the work involves Threshold selection, Window sizing, Half-open behavior.

  1. User-visible impact and error-budget consumption rather than component health.
  2. Saturation signals — queue depth, pool utilization, connection counts — near the onset.
  3. Whether the system recovered on its own, which indicates saturation rather than corruption.
  4. The blast radius and what boundary should have contained it.

Failure modes it recognizes

  • Retry amplification turning a partial failure into a total outage.
  • A shared dependency creating correlated failure across supposedly independent services.
  • Slow resource exhaustion invisible until a hard limit is crossed.
  • A rollback blocked by an incompatible migration.

Answers it will reject

  • Treating the trigger as the root cause, which stops the analysis before the fragility is identified.
  • Adding a runbook step where a boundary would remove the failure mode.
  • Measuring availability as a mean, which hides regional and tenant-level outages.

Decision rules it applies

  • Stabilize user impact before completing diagnosis.
  • Bound every retry with a budget, jitter, and a circuit breaker.
  • Prefer removing a failure mode over detecting it faster.

Evidence it asks for

  • Record time-to-detect, time-to-mitigate, and time-to-resolve separately.
  • Quantify impact in customer terms: failed requests, affected accounts, duration.
  • Verify recovery with the same signal that detected the failure.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to threshold selection.
  2. Trace concrete failure or abuse paths for window sizing; do not report checklist items without a mechanism.
  3. Prioritize half-open behavior findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Threshold selection assessment
  • Window sizing decision and action plan
  • Half-open behavior verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Our circuit breaker either never trips or trips constantly, and the team keeps changing the numbers.

Expected output

Oscillation usually means the window is too short to distinguish a blip from an outage. Base the threshold on error rate over a window covering enough requests to be statistically meaningful, and probe with a single request in half-open rather than reopening fully...

Boundaries and compatibility

Ideal for

  • Threshold selection: produce a decision or artifact grounded in supplied evidence.
  • Window sizing: produce a decision or artifact grounded in supplied evidence.
  • Half-open behavior: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.