resilience-patterns

Explain sizing of circuit breakers, timeouts, and retries for external API integrations.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/kssumin/claude-playground --skill resilience-patterns-kssumin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resilience-patterns
Source: https://github.com/kssumin/claude-playground/tree/main/.claude/skills/resilience-patterns
Command: npx skills add https://github.com/kssumin/claude-playground --skill resilience-patterns-kssumin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides principled guidance for configuring resilience controls (circuit breakers, timeouts, and retries) by explaining the rationale behind chosen values, rather than focusing on implementation details. It covers threshold derivation, ignoreExceptions traps, separation of timeout and circuit breaker responsibilities, and retry target selection for external API integration.

Core Features & Use Cases

  • Guidance on sizing circuit breakers based on observed steady-state failure rates rather than arbitrary numbers.
  • Clear criteria for when to retry, which exceptions to record or ignore, and how to separate timeout handling from breaker state.
  • Applicability to API clients and asynchronous pipelines (e.g., Kafka) to reduce oscillation and lag through tuned thresholds and probe settings.
  • Practical anti-patterns and best practices with concrete examples.

Quick Start

Provide sizing guidance for circuit breakers and timeouts based on observed failure rates to design a robust external API integration.

Frequently Asked Questions about resilience-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I size circuit breaker thresholds for external API integrations?

Size circuit breaker thresholds based on observed steady-state failure rates rather than arbitrary numbers to derive robust external API integration configurations that reduce oscillation.

What are the ignoreExceptions traps when configuring resilience controls?

ignoreExceptions traps occur when configuring circuit breakers without clear criteria for which exceptions to record or ignore, leading to improper breaker state transitions and masked downstream failures.

How do I separate timeout and circuit breaker responsibilities in API clients?

Separate timeout and circuit breaker responsibilities by treating timeouts as request-level controls and breakers as system-level state managers, preventing overlapping failure detection logic in API clients.

When should I retry failed requests in asynchronous pipelines?

Retry failed requests in asynchronous pipelines by selecting retry targets carefully based on exception types and failure characteristics, applying tuned thresholds to reduce lag and oscillation.

Can I apply these resilience patterns to Kafka asynchronous pipelines?

Yes, these resilience patterns apply to asynchronous pipelines like Kafka by providing tuned thresholds and probe settings that reduce lag and oscillation through principled circuit breaker and timeout configurations.

Why does my circuit breaker keep tripping unexpectedly with downstream API failures?

Your circuit breaker may trip unexpectedly due to improperly derived thresholds not aligned with steady-state failure rates, or ignoreExceptions traps masking transient downstream API failures from the breaker state.