customerio-upgrade-migration
Plan and execute Customer.io SDK upgrades and migrations. Use when upgrading customerio-node versions, migrating from legacy APIs, or updating to new SDK patterns. "update customer.io sdk", "customer.io breaking changes". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-upgrade-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Customer.io Upgrade & 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
What does the customerio-upgrade-migration skill do?
Plan and execute Customer.io SDK upgrades and migrations. Use when upgrading customerio-node versions, migrating from legacy APIs, or updating to new SDK patterns. "update customer.io sdk", "customer.io breaking changes". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-upgrade-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
