Agent skill · software engineering · jeremylongshore
klaviyo-deploy-integration
Deploy Klaviyo integrations to Vercel, Fly.io, and Cloud Run platforms.
Why this skill is useful
Adds specific deployment commands and configuration patterns for Klaviyo integrations across multiple platforms that the AI wouldn't reliably generate on its own.
What it needs
Requires fly, gcloud, vercel installed locally. Requires klaviyo account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Klaviyo Deploy Integration Overview Deploy Klaviyo-powered applications to Vercel, Fly.io, and Google Cloud Run with proper secrets management and health checks. Every platform follows the same shape — store the private key + webhook secret, wire a config file, deploy, verify. The lean skeleton lives here; full per-platform recipes live in references/platform-deployments.md. Prerequisites Klaviyo production API key (pk) Platform CLI installed (vercel, fly, or gcloud) Application tested with klaviyo-api SDK klaviyo-prod-checklist completed Instructions The workflow is identical across platforms; only the CLI verbs change. Read the target platform's section in references/platform-deployments.md, then: 1. Store secrets — inject KLAVIYOPRIVATEKEY and KLAVIYOWEBHOOKSIGNINGSECRET via the platform's secret store (vercel env add, fly secrets set, or gcloud secrets create). Never commit these to the repo. 2. Write the platform config — use Write/Edit to create vercel.json, fly.toml, or a Dockerfile that binds the secrets and exposes a health path. See the reference for the exact file contents. 3. Add the universal health check — expose src/health.ts (identical on all platforms) at the path each platform probes (/api/health on Vercel, /health on Fly.io and Cloud Run). 4. Deploy — run vercel --prod, fly deploy, or gcloud run deploy. 5. Verify — curl the health endpoint and confirm services.klaviyo.connected is true. Vercel skeleton (first example) Fly.io (fly secrets set + fly.toml + fly deploy) and Cloud Run (gcloud secrets create + Dockerfile + gcloud run deploy --set-secrets) follow the same five steps — full commands and config files are in the reference walkthroughs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/klaviyo-deploy-integration