Agent skill · marketing growth · mvanhorn
pp-klaviyo
Klaviyo from the shell, with local customer-behavior analytics layered on top. Trigger phrases: `inspect a Klaviyo profile`, `deploy a Klaviyo campaign`, `check Klaviyo flow decay`, `reconcile Klaviyo campaign revenue`.
Why this skill is useful
Adds a CLI tool with unique commands for managing Klaviyo campaigns and analyzing customer behavior that aren't available in public documentation.
What it needs
Requires klaviyo-pp-cli installed locally. About 10k tokens when loaded. Last updated 2026-08-06. 1,890 stars on the source repository.
What this skill does
<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/marketing/klaviyo/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". --> Klaviyo - Printing Press CLI Prerequisites: Install the CLI This skill drives the klaviyo-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows: 2. Verify: klaviyo-pp-cli --version 3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill. If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer): If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds. When to Use This CLI Use this CLI when an agent needs to inspect or operate Klaviyo without the web UI, especially for profiles, events, campaigns, flows, segments, templates, metrics, and compound growth workflows. Generated with Printing Press 4.35.4 against Klaviyo API revision 2026-10-15. Every request sends revision: 2026-10-15. At this revision, a campaign is a container. Messages carry status and send time; campaign-audiences carry included and excluded lists and segments; variations carry channel, template, subject, and sender. IDs issued before 2026-10-15 are now message IDs. Campaign workflows accept either a container ID or a historical campaign/message ID and resolve its audiences and variations. The raw campaigns get-id read expects a container ID and explains historical IDs on a 404. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mvanhorn/pp-klaviyo