Agent skill · software engineering · jeremylongshore
klaviyo-debug-bundle
Collect Klaviyo debug evidence for support tickets and troubleshooting.
Why this skill is useful
Adds an executable script for collecting Klaviyo diagnostic information that automates troubleshooting and support ticket preparation.
What it needs
Requires curl, python3, tar installed locally. Requires klaviyo account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Klaviyo Debug Bundle Overview Collect all diagnostic information needed for a Klaviyo support ticket into one redacted, shareable tarball: SDK version, API connectivity, auth result, rate limit status, recent errors, and environment config. Every secret (API keys, emails, phone numbers, webhook secrets) is redacted before packaging, so the bundle is safe to attach to a ticket. The workflow builds a single shell script (klaviyo-debug-bundle.sh) in five steps, then runs it. The full script and a programmatic TypeScript alternative live in the reference files linked below. Prerequisites The klaviyo-api SDK installed (npm list klaviyo-api to confirm). The KLAVIYOPRIVATEKEY environment variable set to a private API key. Read access to your application's log directory (defaults scanned: logs/, /var/log/app/). curl, tar, and python3 available on the host. Instructions Assemble the five blocks below (verbatim from the reference) into one klaviyo-debug-bundle.sh, make it executable, and run it from your application root so the log-collection step can find logs/. 1. Create the bundle dir — timestamped klaviyo-debug-YYYYMMDD-HHMMSS/ and a summary.txt header. 2. Collect environment info — Node/npm/OS versions, klaviyo-api SDK version, and a redacted API-key presence check. 3. Run connectivity tests — DNS resolve, an authenticated GET /api/accounts/ (captures the HTTP code), rate-limit headers, and the Klaviyo status page. 4. Collect logs — grep known log dirs for Klaviyo errors, redacting keys and emails inline. 5. Package and clean up — tar -czf the dir, remove the working copy, print the tarball path. The skeleton of step 1: See the full shell implementation for all five steps verbatim. To collect the same signals as a structured object (SDK version, connectivity, latency) instead of a tarball, use the TypeScript helper in examples. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/klaviyo-debug-bundle