skills.rest
mymx2
mymx2COMMUNITY
Explore all skills by this author →
GitHub

integration-resilience-engineer

Design resilient Kotlin and Spring integrations with timeout budgets, retries, and circuit breakers.

4|Updated Jun 10, 2026
Search Tags:#resilience#kotlin#distributed-systems#idempotency#spring#circuit-breaker
One-click install
npx skills add https://github.com/mymx2/foreman --skill integration-resilience-engineer-mymx2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-resilience-engineer
Source: https://github.com/mymx2/foreman/tree/main/.qoder/skills.collected/skills/integration-resilience-engineer
Command: npx skills add https://github.com/mymx2/foreman --skill integration-resilience-engineer-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the fragility of distributed systems by providing a structured framework to handle partial failures, timeouts, and unreliable external dependencies in Kotlin and Spring environments.

Core Features & Use Cases

  • Resilience Strategy Design: Implements circuit breakers, bulkheads, and exponential backoff with jitter to prevent cascading failures.
  • Idempotency & Messaging: Provides patterns for safe retries and deduplication in message-driven architectures to ensure data consistency.
  • Use Case: When integrating a critical payment gateway that experiences intermittent latency, use this skill to define a robust retry budget and circuit breaker policy that prevents system-wide thundering herds.

Quick Start

Use the integration-resilience-engineer skill to design a fault-tolerant integration strategy for the new external API client.

Frequently Asked Questions about integration-resilience-engineer

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

FAQPage Schema
How do I design circuit breakers and retry policies for Spring services?▼

You design circuit breakers and retry policies for Spring services by defining explicit timeout budgets, exponential backoff with jitter, and bulkheads to prevent cascading failures in distributed workflows.

How do I prevent thundering herds when integrating with unstable external systems?▼

You prevent thundering herds when integrating with unstable external systems by applying circuit breakers and robust retry budgets that isolate failures and stop system-wide resource exhaustion during latency spikes.

Does this resilience strategy apply to scheduled and messaging integrations in Kotlin?▼

Yes, this resilience strategy applies to scheduled and messaging integrations in Kotlin by providing structured patterns for fault-tolerant background task processing and high-concurrency distributed workflows.

What's the best way to analyze failure modes for distributed integrations?▼

The best way to analyze failure modes for distributed integrations is to evaluate observability standards and strict idempotency rules, ensuring production-grade reliability when handling timeouts and unreliable dependencies.

Related Skills

Explore More Software Engineering Skills→
kbrgnjkbrgnj
14

project-context-ingestion

Map Kotlin and Spring repository modules and dependencies into a project brief.

Community
Advanced
Prathmesh2000Prathmesh2000
1

resilience-patterns

Implement circuit breakers, retries, bulkheads, and fallbacks for distributed services.

Community
Advanced
vasilyu1983vasilyu1983
73

qa-resilience

Implement resilience patterns like circuit breakers and retries for distributed systems.

Community
Advanced
ahgraberahgraber
5

python-integrations-resilience

Enforce explicit timeouts, retries, and idempotency for Python outbound API integrations.

Community
Advanced