resilient-third-party-integrations

Implement resilient outbound integrations with anti-corruption layers, timeouts, retries, and circuit breakers.

1|1|Updated Mar 6, 2026

Search Tags:#integration #resilience #idempotency #third-party #retry #circuit-breaker #acl

Ready to run

npx skills add https://github.com/eymass/swe-plugin --skill resilient-third-party-integrations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resilient-third-party-integrations
Source: https://github.com/eymass/swe-plugin/tree/main/skills/swe-third-party-integration
Command: npx skills add https://github.com/eymass/swe-plugin --skill resilient-third-party-integrations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds and hardens outbound integrations with external APIs and service providers so your core domain remains reliable in the face of vendor failures, latency, and drift.

Core Features & Use Cases

Anti-Corruption Layer (ACL) to shield domain logic from provider quirks and drift.
Spec pinning and stable clients by embedding and freezing OpenAPI/proto contracts to prevent drift.
Timeouts, retries with backoff and jitter, and circuit breakers to absorb provider failures and isolate outages.
Idempotency keys, outbox pattern, and dead-letter queues to ensure safe retries and reliable async workflows.
Observability with distributed tracing, metrics, and structured logs to own integration health.

Quick Start

Design and implement a resilient outbound integration to a chosen vendor API using an ACL, timeouts, and retries.

Frequently Asked Questions about resilient-third-party-integrations

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

FAQPage Schema

How do I design resilient third-party API integrations that handle vendor failures?▼

To prevent API drift in third-party integrations, use spec pinning by embedding and freezing OpenAPI or proto contracts. This establishes stable clients and ensures your anti-corruption layer remains unaffected by upstream provider changes.

How do I ensure idempotency and safe retries for outbound payment processor integrations?▼

To ensure idempotency and safe retries for payment processor integrations, utilize idempotency keys and the outbox pattern. Implement dead-letter queues to capture failures and guarantee reliable asynchronous workflow execution without duplicate transactions.

What is an anti-corruption layer and when do I need it for external webhooks?▼

An anti-corruption layer is a boundary that shields your core domain logic from external provider quirks. You need it for external webhooks and APIs to prevent vendor drift and systemic failures from polluting your internal architecture.

What's the best way to monitor integration health and observability for external APIs?▼

The best way to monitor external API integration health is to implement comprehensive observability using distributed tracing, metrics, and structured logs. This ensures you own integration health and can quickly identify latency or failure points.

Do I need an anti-corruption layer if my external provider API is highly reliable?▼

Yes, you still need an anti-corruption layer even with reliable providers. It enforces domain isolation, prevents unexpected drift from API updates, and ensures safe failure modes, maintaining core domain stability regardless of vendor uptime.