Agent skill · marketing growth · jeremylongshore
customerio-core-feature
Implement Customer.io core features: transactional messages,
Why this skill is useful
Provides specific API commands and workflows for implementing Customer.io features that the AI wouldn't reliably generate on its own.
What it needs
Requires customerio-node installed locally. Requires customer.io account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Customer.io Core Features Output A scoped, consent-aware Customer.io feature configuration with a validated data contract and owner. A test receipt showing intended audience, environment, event/message behavior, and safe rollback path. Examples Configure a feature in development with a synthetic profile and a narrowly defined event. Verify attributes, segment membership, and message preview before promotion. If the audience or consent behavior differs from expectation, disable the development configuration and correct the contract before proceeding. Overview Implement Customer.io's key platform features: transactional emails/push (password resets, receipts), API-triggered broadcasts (one-to-many on demand), segment-driving attributes, anonymous-to-known user merging, and person suppression/deletion. Prerequisites customerio-node installed Track API credentials (CUSTOMERIOSITEID + CUSTOMERIOTRACKAPIKEY) App API credential (CUSTOMERIOAPPAPIKEY) — required for transactional + broadcasts Instructions Feature 1: Transactional Email Transactional messages are opt-in-implied messages (receipts, password resets). Create the template in Customer.io dashboard first, then call the API with data. Dashboard setup: Create transactional message at Transactional > Create Message. Use Liquid syntax: {{ data.reseturl }}, {{ data.orderid }}, {% for item in data.items %}. Feature 2: Transactional Push Feature 3: API-Triggered Broadcasts Broadcasts send to a pre-defined segment on demand. Define the segment and message in the dashboard, then trigger via API. Feature 4: Segment-Driving Attributes Segments in Customer.io are data-driven — they automatically include/exclude people based on attributes you set via identify(). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-core-feature