Agent skill · software engineering · jeremylongshore
customerio-upgrade-migration
Plan and execute Customer.io SDK upgrades and migrations.
Why this skill is useful
Provides specific migration patterns and code examples for upgrading the customerio-node SDK that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Customer.io Upgrade & Migration Output A staged migration record with schema/template compatibility, environment evidence, owner, and rollback decision. A preserved prior configuration and safe observation window before any irreversible cleanup. Examples Migrate a development workspace first using synthetic profiles and versioned event/template contracts. Verify delivery, consent, attributes, and observability before staging and production canaries. If compatibility or recipient behavior differs, roll back to the prior version and stop promotion; do not bulk-replay production events to test a migration. Current State !npm list customerio-node 2>/dev/null grep customerio echo 'customerio-node: not installed' !npm view customerio-node version 2>/dev/null echo 'Cannot check latest version' Overview Plan and execute customerio-node SDK upgrades safely: assess current version, review breaking changes, apply code migrations, and validate with staged rollout. Prerequisites Current SDK version identified (npm list customerio-node) Test environment available Version control for rollback Major Version Migration Reference Legacy CustomerIO to Modern TrackClient + APIClient Older versions of customerio-node used a single CustomerIO class. Modern versions split into TrackClient (tracking) and APIClient (transactional/broadcasts). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-upgrade-migration