Agent skill · software engineering · sickn33
api-integration
Designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services.
Why this skill is useful
Provides specific patterns and code snippets for event-driven architecture and API integration that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
API Integration Skill When to Use Use this skill when you need designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services. Use whenever the user asks about webhooks, event streaming, API composition, connecting two or more APIs, building pipelines, Pub/Sub, Kafka topics, ETL... Design integration patterns, webhook flows, event pipelines, and API composition strategies. --- Webhook Design Outbound Webhook Endpoint (from your system to 3rd party) Payload envelope Signature verification (receiver side): Inbound Webhook Registration API --- API Chaining / Composition Pattern Always: handle failures at each step independently, use idempotency keys, implement retry with exponential backoff. --- Event-Driven Architecture Event Schema (CloudEvents spec) Topics / Queues design Topic Producers Consumers Retention ------- ----------- ----------- ----------- orders.created orders-svc payments-svc, email-svc 7 days payments.completed payments-svc orders-svc, ledger-svc 30 days users.deleted users-svc all services 90 days --- Saga Pattern (Distributed Transaction) --- Outbox Pattern (reliable event publishing) --- Integration Checklist [ ] Idempotency keys on all state-changing calls [ ] Retry with exponential backoff (base 1s, max 60s, jitter) [ ] Circuit breaker (open after 5 failures in 10s) [ ] Dead-letter queue for unprocessable events [ ] Webhook delivery logging + manual replay endpoint [ ] Schema versioning on all events [ ] Correlation IDs on all inter-service calls --- Handoff Report the event schemas, delivery/retry policy, idempotency and compensation boundaries, and the checks actually performed. Signature verification also needs the provider's current protocol, bounded input, timestamp/replay protection and an authorized test endpoint. A design is not evidence that an integration or payment ran. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/api-integration--c77458