Individual skill

customerio-reference-architecture

Implement Customer.io enterprise reference architecture. Use when designing integration layers, event-driven architectures, or enterprise-grade Customer.io setups. Trigger: "customer.io architecture", "customer.io design", "customer.io enterprise", "customer.io integration pattern".

skills/.curated/customerio-reference-architecture/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,916
Repository last updated: Nov 12, 2026
License: MIT

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

ai Repository topic
automation Repository topic
claude-code Repository topic
devops Repository topic
mcp Repository topic
ai-agents Repository topic
anthropic Repository topic
claude-code-plugins Repository topic
developer-tools Repository topic
llm Repository topic
saas Declared skill tag
customer-io Declared skill tag
architecture Declared skill tag
enterprise Declared skill tag
engineering Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 12,057 bytes
references/implementation-guide.mddoc · 9,793 bytes

Read excerpt

# Customer.io Reference Architecture

## Prerequisites

- A data-flow owner, approved workspace/environment boundaries, event contract, consent model, and incident/support route.
- Repository/configuration review for any change to credentials, webhooks, message templates, or customer-data processing.

## Output

- A documented architecture mapping event producers, identity/consent, Customer.io workspaces, observability, ownership, and failure handling.
- Clear trust boundaries and reversible integration points for delivery, replay, and incident response.

## Examples

Document a producer that validates and idempotently emits a versioned event to the development workspace, with a consent gate before campaign entry and redacted metrics by environment. Promote the same contract through staging before production, retain a dead-letter/replay owner, and keep recipient identifiers and tokens outside logs and diagrams.