New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Klaviyo Upgrade Migration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Upgrade Klaviyo SDK versions and migrate between API revisions.

MITAuto-check passedMarketing & SEO

Install Klaviyo Upgrade Migration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill klaviyo-upgrade-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace klaviyo-upgrade-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/klaviyo-upgrade-migration .claude/skills/klaviyo-upgrade-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
klaviyo-upgrade-migration
GitHub stars
2.8k
Token cost
~1.7k tokens
SKILL.md length
595 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Upgrade Klaviyo SDK versions and migrate between API revisions.

  • Works in 5 steps: Assess the current state → Find affected usage → Apply the matching migration pattern → …
  • Upgrading the klaviyo-api package
  • SKILL.md covers Overview, Prerequisites, Klaviyo API Revision Timeline and Instructions, plus 5 more sections
  • Calls npm, npx and git; needs KLAVIYO_PRIVATE_KEY

What it does

Klaviyo Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade Klaviyo SDK versions and migrate between API revisions. Use when upgrading the klaviyo-api package, migrating from v1/v2 legacy APIs to the current REST API, or handling breaking changes between revisions. Trigger with phrases like "upgrade klaviyo", "klaviyo migration", "klaviyo breaking changes", "update klaviyo SDK", "klaviyo API revision".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/migration-patterns.md` and `references/upgrade-procedure.md`). Compatibility notes: Designed for Claude Code

It sits in Marketing & SEO, covering Email marketing. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Upgrading the klaviyo-api package
  • Migrating from v1/v2 legacy APIs to the current REST API
  • Handling breaking changes between revisions
  • With phrases like upgrade klaviyo

Example prompts

  • “upgrade klaviyo”
  • “klaviyo migration”
  • “klaviyo breaking changes”
  • “/klaviyo-upgrade-migration”

Requirements

  • Node.js
  • A credential in KLAVIYO_PRIVATE_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Edit, Bash(npm:*), Bash(git:*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Assess the current state
  2. Find affected usage
  3. Apply the matching migration pattern
  4. Upgrade, verify, and ship
  5. Roll back if needed

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Edit
    • Bash(npm:*)
    • Bash(git:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • npx
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • developers.klaviyo.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • KLAVIYO_PRIVATE_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Klaviyo Upgrade Migration loads about 1.7k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 595 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 595 words, ~1,658 tokens.

Download SKILL.mdSave it as .claude/skills/klaviyo-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
klaviyo-upgrade-migration
description
Upgrade Klaviyo SDK versions and migrate between API revisions. Use when upgrading the klaviyo-api package, migrating from v1/v2 legacy APIs to the current REST API, or handling breaking changes between revisions. Trigger with phrases like "upgrade klaviyo", "klaviyo migration", "klaviyo breaking changes", "update klaviyo SDK", "klaviyo API revision".
allowed-tools
Read, Edit, Bash(npm:*), Bash(git:*)
compatibility
Designed for Claude Code
version
1.7.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, klaviyo, email-marketing, cdp

Klaviyo Upgrade & Migration

Overview

Guide for upgrading the klaviyo-api SDK, migrating from legacy v1/v2 APIs, and handling breaking changes between Klaviyo API revisions. The workflow assesses the current version, surfaces breaking changes with the TypeScript compiler, applies the matching migration pattern, and ships behind a staging deploy with a clean rollback.

Deep before/after code and the full command sequence live in references/ so this file stays a scannable map of the workflow:

  • Migration patterns — legacy v1/v2 → current API, SDK major upgrade (ConfigWrapper → ApiKeySession), property casing.
  • Upgrade & rollback procedure — pinned install, tsc/test gates, staging deploy, rollback, migration checklist.

Prerequisites

  • The klaviyo-api package installed and a known current version (npm list klaviyo-api).
  • Git available, with a clean working tree so the upgrade lands on its own branch.
  • A working test suite (npm test), and ideally a staging integration test target.
  • A Klaviyo private API key in the environment for integration verification.

Klaviyo API Revision Timeline

Each revision is supported for 2 years after release. Plan to move to the latest every 12-18 months so you never fall inside the deprecation window.

RevisionReleasedDeprecatedKey Changes
2024-10-15Oct 2024Oct 2026Reporting API, campaign message updates
2024-07-15Jul 2024Jul 2026Custom objects, tracking settings
2024-02-15Feb 2024Feb 2026Bulk operations, segments V2
2023-12-15Dec 2023Dec 2025Profile subscription changes
2023-07-15Jul 2023Jul 2025Relationship endpoint restructuring

Instructions

Step 1: Assess the current state

Compare what is installed against what is published to size the jump. A single major step is routine; skipping several majors means expect casing and import changes.

bash
npm list klaviyo-api          # e.g. klaviyo-api@15.0.0
npm view klaviyo-api version  # latest, e.g. 21.0.0
Step 2: Find affected usage

Read the releases changelog for the target major, then locate the call sites that will need edits.

bash
grep -rn "from 'klaviyo-api'" src/
grep -rn "ApiKeySession\|ConfigWrapper\|ProfilesApi\|EventsApi" src/
Step 3: Apply the matching migration pattern

Pick the pattern that fits the errors you see and edit each call site. Full before/after code is in migration patterns:

  • Legacy v1/v2 → current API — replace raw /api/v2/... HTTP calls with typed EventsApi / ProfilesApi resource classes.
  • SDK major upgrade — swap the global ConfigWrapper('pk_***') for a per-instance new ApiKeySession('pk_***') passed to each *Api.
  • Property casing — rename snake_case attributes (first_name) to camelCase (firstName).
Show full SKILL.md (243 more words)Show less
Step 4: Upgrade, verify, and ship

Install the target version pinned, let tsc and the test suite gate the change, and deploy to staging before production. Full commands: upgrade procedure.

bash
git checkout -b upgrade/klaviyo-api-v21
npm install klaviyo-api@21.0.0 --save-exact
npx tsc --noEmit 2>&1 | grep -i "klaviyo\|error TS"   # find breaking changes
npm test
Step 5: Roll back if needed

If error rates rise after the upgrade, reinstall the previous exact version — see the rollback procedure. Because Step 4 pinned versions, rollback is a clean reinstall with no dependency guesswork.

Output

Running this workflow produces:

  • An upgrade/klaviyo-api-vNN branch with package.json + package-lock.json pinned to the target version via --save-exact.
  • Edited call sites in src/ using the current ApiKeySession pattern and camelCase attributes, with npx tsc --noEmit clean.
  • A green npm test (and staging test:integration) run confirming the migration.
  • A commit deployed to staging first, with a documented rollback commit ready if 24-hour error monitoring flags a regression.

Error Handling

IssueCauseSolution
TypeError: ConfigWrapper is not a functionOld SDK patternSwitch to ApiKeySession pattern
Property 'first_name' does not existCasing changeUse firstName (camelCase)
response.data is undefinedAccess pattern changeUse response.body.data
revision not supportedDeprecated revisionUpdate revision header value

Examples

Migrate a v2 identify call to the current SDK. After grep finds a legacy /api/identify call, replace it with createOrUpdateProfile:

typescript
import { ApiKeySession, ProfilesApi, ProfileEnum } from 'klaviyo-api';

const session = new ApiKeySession(process.env.KLAVIYO_PRIVATE_KEY!);
const profilesApi = new ProfilesApi(session);
await profilesApi.createOrUpdateProfile({
  data: {
    type: ProfileEnum.Profile,
    attributes: { email: 'user@example.com', firstName: 'Jane', properties: { plan: 'pro' } },
  },
});

The full set of before/after examples — event tracking, the ConfigWrapper → ApiKeySession upgrade, and property casing — is in migration patterns.

Resources

Next Steps

For wiring these upgrade checks into continuous integration, see the klaviyo-ci-integration skill.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/klaviyo-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/migration-patterns.md
  • references/upgrade-procedure.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Klaviyo Upgrade Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Klaviyo Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Klaviyo Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: PassMIT
Email Sequencefreekmurze/dotfiles1k19 repos~2kAutomated safety check: PassNone
Emailscoreyhaines31/marketingskills54k1 repos~2.8kAutomated safety check: PassMIT
Email SequenceLeoYeAI/openclaw-marketing-skills1k2 repos~2.1kAutomated safety check: PassCustom licence
Onboarding Crofreekmurze/dotfiles1k16 repos~1.6kAutomated safety check: PassNone
Marketing OsYuzzyuk/marketing-os540—~2.5kAutomated safety check: PassMIT

Similar skills

  • Email Sequence

    freekmurze/dotfiles

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    1k GitHub starsUsed in 19 repos~2k tokens
    Marketing & SEOAuto-check passed

  • Emails

    coreyhaines31/marketingskills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    54k GitHub starsUsed in 1 repo~2.8k tokens
    Marketing & SEOAuto-check passed

  • Email Sequence

    LeoYeAI/openclaw-marketing-skills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    1k GitHub starsUsed in 2 repos~2.1k tokens
    Marketing & SEOAuto-check passed

  • Onboarding Cro

    freekmurze/dotfiles

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    1k GitHub starsUsed in 16 repos~1.6k tokens
    Marketing & SEOAuto-check passed

  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    540 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Onboarding

    Nexus-JPF/note-companion

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    870 GitHub starsUsed in 4 repos~1.6k tokens
    Marketing & SEOAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Klaviyo Upgrade Migration

What does Klaviyo Upgrade Migration do?

Upgrade Klaviyo SDK versions and migrate between API revisions. Klaviyo Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade Klaviyo SDK versions and migrate between API revisions.

When should I use Klaviyo Upgrade Migration?

Klaviyo Upgrade Migration fits situations like: upgrading the klaviyo-api package; migrating from v1/v2 legacy APIs to the current REST API; handling breaking changes between revisions; with phrases like upgrade klaviyo.

How do I install Klaviyo Upgrade Migration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill klaviyo-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/klaviyo-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/klaviyo-upgrade-migration in your project. Claude Code loads it when a task matches its description.

How do I install Klaviyo Upgrade Migration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill klaviyo-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/klaviyo-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/klaviyo-upgrade-migration in your project. Codex loads it when a task matches its description.

Can I use Klaviyo Upgrade Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill klaviyo-upgrade-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/klaviyo-upgrade-migration, .gemini/skills/klaviyo-upgrade-migration, .github/skills/klaviyo-upgrade-migration and .opencode/skills/klaviyo-upgrade-migration in your project.

What does Klaviyo Upgrade Migration need to run?

Going by SKILL.md and its folder, Klaviyo Upgrade Migration needs the command-line tools its instructions call (npm, npx and git) and credentials named KLAVIYO_PRIVATE_KEY. Our summary lists: Node.js; A credential in KLAVIYO_PRIVATE_KEY. Its frontmatter pre-approves these tools: Read, Edit, Bash(npm:*), Bash(git:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Klaviyo Upgrade Migration access the network?

SKILL.md names 2 domains. As links in the text: developers.klaviyo.com and github.com. This is read from the text; nothing was executed.

Is Klaviyo Upgrade Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Klaviyo Upgrade Migration use?

Klaviyo Upgrade Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Klaviyo Upgrade Migration use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Klaviyo Upgrade Migration?

Skills that share tags, products or a category with Klaviyo Upgrade Migration: Email Sequence (freekmurze/dotfiles, 1k stars), Emails (coreyhaines31/marketingskills, 54k stars), Email Sequence (LeoYeAI/openclaw-marketing-skills, 1k stars) and Onboarding Cro (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Klaviyo Upgrade Migration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.