Agent skill · software engineering · jeremylongshore
customerio-reliability-patterns
Implement Customer.io reliability and fault-tolerance patterns.
Why this skill is useful
Adds executable scripts for implementing fault-tolerance patterns specifically for Customer.io integrations, which are not commonly found in public documentation.
What it needs
Requires redis installed locally. Requires customer.io account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Customer.io Reliability Patterns Output An idempotent, observable event-delivery design with owned retry, replay, and dead-letter decisions. A recovery procedure that protects consent, ordering, and recipient experience during partial failures. Error Handling Condition Safe response --- --- Provider returns transient failure Retry with bounded exponential backoff and preserve the idempotency key. Event may be duplicated Deduplicate by the stable event/correlation key before triggering downstream action. Replay could resend customer messaging Require consent/segment review and replay only the scoped failed set. Dead-letter queue grows Alert the owner, quarantine malformed payloads, and fix the contract before bulk replay. Examples Store an immutable event ID and delivery state, retry 429/5xx responses with bounded backoff, and send terminal failures to a protected dead-letter queue. After the schema fix, replay only those records whose consent and idempotency checks still pass. Overview Implement fault-tolerant Customer.io integrations: circuit breaker (stop cascading failures), retry with jitter (handle transient errors), fallback queue (survive outages), idempotency guard (prevent duplicates), and graceful degradation (never crash your app for analytics). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-reliability-patterns