Klaviyo Local Dev Loop

What it does

When your agent uses it

• Setting up a development environment
• Configuring test workflows
• Establishing a fast iteration cycle with the Klaviyo API
• With phrases like klaviyo dev setup

Example prompts

• “klaviyo dev setup”
• “klaviyo local development”
• “klaviyo dev environment”
• “/klaviyo-local-dev-loop”

Requirements

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

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Project structure — create src/klaviyo/ for SDK modules and tests/{unit,integration}/. Keep secrets in a git-ignored .env.local, ship a…
2. 2Environment configuration — define KLAVIYO_PRIVATE_KEY / KLAVIYO_PUBLIC_KEY and wire the dev, test, test:watch, test:integration, and…
3. 3SDK client singleton — read the key once, cache the ApiKeySession, and export lazy per-API accessors so you only instantiate what you use
4. 4Unit testing with mocks — vi.mock('klaviyo-api', ...) the whole SDK so unit tests are deterministic and offline. See test examples.
5. 5Integration test — a describe.skipIf(!process.env.KLAVIYO_TEST) suite that exercises the live account. See test examples.
6. 6Hot reload development — run npm run dev (tsx watch) in one terminal and npm run test:watch in another for a tight edit-test cycle.

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
  • Write
  • Edit
  • Bash(npm:*)
  • Bash(pnpm:*)
  • Bash(npx:*)
  • Grep

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npm
  • tsx

  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):

  • github.com
  • vitest.dev

  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
  • KLAVIYO_PUBLIC_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 Local Dev Loop loads about 1.4k 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 434 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.4k

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

• NoteMentions a .env fileSKILL.md:41

  project layout, `.env` templates, `package.json` scripts, and the client

• NoteMentions a .env fileSKILL.md:45

  ation}/`. Keep secrets in a git-ignored `.env.local`, ship a committed `.env.example`.

• NoteMentions a .env fileSKILL.md:80

  `KLAVIYO_PRIVATE_KEY not set` | Missing .env.local | Copy from .env.example |

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). 434 words, ~1,358 tokens.

name

klaviyo-local-dev-loop

description

Configure Klaviyo local development with hot reload, mocking, and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with the Klaviyo API. Trigger with phrases like "klaviyo dev setup", "klaviyo local development", "klaviyo dev environment", "develop with klaviyo", "klaviyo testing".

allowed-tools

Read, Write, Edit, Bash(npm:*), Bash(pnpm:*), Bash(npx:*), Grep

compatibility

Designed for Claude Code

version

1.7.0

license

MIT

author

Jeremy Longshore <jeremy@intentsolutions.io>

tags

saas, klaviyo, email-marketing, cdp

// tests/unit/profiles.test.ts
import { describe, it, expect, vi } from 'vitest';

vi.mock('klaviyo-api', () => ({
  ApiKeySession: vi.fn(),
  ProfilesApi: vi.fn().mockImplementation(() => ({
    createProfile: vi.fn().mockResolvedValue({
      body: { data: { id: '01JMOCKPROFILEID', attributes: { email: 'test@example.com' } } },
    }),
  })),
}));

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

describe('Profile operations', () => {
  it('creates a profile with email', async () => {
    const api = new ProfilesApi(new ApiKeySession('pk_test_key'));
    const result = await api.createProfile({
      data: { type: 'profile' as any, attributes: { email: 'test@example.com' } },
    });
    expect(result.body.data.id).toBe('01JMOCKPROFILEID');
  });
});

© 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-local-dev-loop of jeremylongshore/tons-of-skills-marketplace.

• SKILL.md
• references/examples.md
• references/implementation.md

Open the folder on GitHubat commit cfae287