Individual skill

customerio-reliability-patterns

Implement Customer.io reliability and fault-tolerance patterns. Use when building circuit breakers, fallback queues, idempotency, or graceful degradation for Customer.io integrations. Trigger: "customer.io reliability", "customer.io resilience", "customer.io circuit breaker", "customer.io fault tolerance".

plugins/saas-packs/customerio-pack/skills/customerio-reliability-patterns/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,917
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# 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. |
Back to top