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 CI Integration

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

Configure CI/CD pipelines for Klaviyo integrations with GitHub Actions.

MITAuto-check passedDevOps & Cloud

Install Klaviyo CI Integration

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace klaviyo-ci-integration --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-ci-integration .claude/skills/klaviyo-ci-integration && 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-ci-integration
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
401 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure CI/CD pipelines for Klaviyo integrations with GitHub Actions.

  • Works in 3 steps: Configure GitHub secrets → Add the CI workflow → Write the tests
  • Setting up automated testing
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 4 more sections
  • Calls gh, git and npm; needs KLAVIYO_PRIVATE_KEY and KLAVIYO_WEBHOOK_SIGNING_SECRET

What it does

Klaviyo CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure CI/CD pipelines for Klaviyo integrations with GitHub Actions. Use when setting up automated testing, configuring CI secrets, or integrating Klaviyo SDK tests into your build pipeline. Trigger with phrases like "klaviyo CI", "klaviyo GitHub Actions", "klaviyo automated tests", "CI klaviyo", "klaviyo pipeline".

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

It sits in DevOps & Cloud, covering Email marketing and CI/CD. It works with GitHub Actions. 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

  • Setting up automated testing
  • Configuring CI secrets
  • Integrating Klaviyo SDK tests into your build pipeline
  • With phrases like klaviyo CI

Example prompts

  • “klaviyo CI”
  • “klaviyo GitHub Actions”
  • “klaviyo automated tests”
  • “/klaviyo-ci-integration”

Requirements

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

Workflow steps

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

  1. Configure GitHub secrets
  2. Add the CI workflow
  3. Write the tests

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(gh:*)
    • Bash(npm:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git
    • npm
    • tsc

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

    • docs.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
    • KLAVIYO_WEBHOOK_SIGNING_SECRET

    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 CI Integration loads about 1.3k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 401 words of instructions outside code blocks.

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

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). 401 words, ~1,272 tokens.

Download SKILL.mdSave it as .claude/skills/klaviyo-ci-integration/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
klaviyo-ci-integration
description
Configure CI/CD pipelines for Klaviyo integrations with GitHub Actions. Use when setting up automated testing, configuring CI secrets, or integrating Klaviyo SDK tests into your build pipeline. Trigger with phrases like "klaviyo CI", "klaviyo GitHub Actions", "klaviyo automated tests", "CI klaviyo", "klaviyo pipeline".
allowed-tools
Read, Write, Edit, Bash(gh:*), Bash(npm:*)
compatibility
Designed for Claude Code
version
1.7.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, klaviyo, email-marketing, cdp

Klaviyo CI Integration

Overview

Set up a GitHub Actions CI/CD pipeline for Klaviyo integrations: mocked unit tests on every pull request, gated integration tests against the real Klaviyo API on main-branch pushes, SDK-version verification, and an API connectivity smoke test.

The workflow follows the standard two-job split — a fast, key-free unit-tests job safe to require on every PR, and an integration-tests job gated so real-API calls never run on fork PRs where secrets are unavailable.

Prerequisites

  • GitHub repository with Actions enabled
  • Klaviyo test API key (from a test/sandbox account)
  • klaviyo-api SDK and Vitest configured in the repository

Instructions

Step 1: Configure GitHub secrets

Store the Klaviyo test credentials as encrypted repository secrets:

bash
gh secret set KLAVIYO_PRIVATE_KEY --body "pk_test_***"
gh secret set KLAVIYO_WEBHOOK_SIGNING_SECRET --body "whsec_test_***"
Step 2: Add the CI workflow

Create .github/workflows/klaviyo-ci.yml with two jobs. The essential skeleton:

yaml
name: Klaviyo Integration CI
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]
jobs:
  unit-tests:        # mocked, runs on every PR, no API key
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: '20', cache: 'npm' }
      - run: npm ci
      - run: npm test -- --coverage
  integration-tests: # real API, gated to main-branch pushes only
    needs: unit-tests
    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
    runs-on: ubuntu-latest
    env:
      KLAVIYO_PRIVATE_KEY: ${{ secrets.KLAVIYO_PRIVATE_KEY }}
      KLAVIYO_TEST: '1'
    steps: [...]

The full workflow — including tsc --noEmit, npm list klaviyo-api version check, the connectivity smoke test, and the branch-protection config — is in the CI workflow reference.

Step 3: Write the tests

Author two suites the workflow drives:

  • Unit tests mock the klaviyo-api SDK (vi.mock) and run with no key.
  • Integration tests hit the real API behind a describe.skipIf guard keyed on KLAVIYO_TEST + KLAVIYO_PRIVATE_KEY, so they skip cleanly when no key is present.

Full, runnable examples for both suites — event-tracking unit test and a create-and-clean-up live profile test — are in the test examples reference.

Output

  • Unit tests run on every PR (mocked, no API key needed)
  • Integration tests run on main-branch pushes only (real API)
  • SDK version verified in CI via npm list klaviyo-api
  • API connectivity smoke test included in the integration job
Show full SKILL.md (144 more words)Show less

Error Handling

IssueCauseSolution
Secret not found in CIMissing gh secret setAdd the secret via repository settings
Integration test 429Rate limited in CIAdd delays between tests, use a dedicated test key
Auth failures in CIWrong secret nameVerify the secret name matches the workflow env var
Test timeoutSlow Klaviyo responseIncrease timeout-minutes on the job step

Examples

Set up CI on a fresh repository. Store the test credentials, drop in the workflow, then let the pipeline gate itself:

bash
gh secret set KLAVIYO_PRIVATE_KEY --body "pk_test_***"
# add .github/workflows/klaviyo-ci.yml (see Step 2 skeleton + full reference)
git add .github/workflows/klaviyo-ci.yml && git commit -m "ci: add Klaviyo pipeline"
git push   # opens a PR → unit-tests run mocked; integration-tests stay gated to main

Run the gated integration suite locally before pushing to main:

bash
export KLAVIYO_TEST=1
export KLAVIYO_PRIVATE_KEY="pk_test_***"
npm run test:integration   # skipIf guard now active → live API exercised

Both example flows are expanded — full workflow YAML in references/ci-workflow.md and the complete unit + integration suites in references/test-examples.md.

Resources

Next Steps

For deployment patterns that build on this pipeline, see the klaviyo-deploy-integration skill in this pack.

© 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-ci-integration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/ci-workflow.md
  • references/test-examples.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Klaviyo CI Integration 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 CI Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Klaviyo CI Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
CI Failure Triage and RepairChachamaru127/claude-code-harness3.2k1 repos~1.1kAutomated safety check: NotesMIT
CI Watchdoglatitude-dev/latitude-llm4.7k—~1.6kAutomated safety check: PassMIT
Megatron-LM CI Failure TriageNVIDIA/Megatron-LM18k—~1.6kAutomated safety check: PassApache-2.0
CI Triagefair-acc/gnuradio4115—~548Automated safety check: PassLGPL-3.0
Deploy Release Testvercel/next.js143k—~1.2kAutomated safety check: PassMIT

Similar skills

  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

  • CI Watchdog

    latitude-dev/latitude-llm

    Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.

    4.7k GitHub stars~1.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Megatron-LM CI Failure Triage

    NVIDIA/Megatron-LM

    Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed

  • CI Triage

    fair-acc/gnuradio4

    Fetch and classify a failed GitHub Actions job for this repo — distinguish out-of-memory kills, six-hour timeouts, configure errors and genuine test failures, and identify what was in flight.

    115 GitHub stars~548 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Deploy Release Test

    vercel/next.js

    Official

    Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow.

    143k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Code Patterns

    Aedelon/claude-code-blueprint

    Reference patterns for REST APIs, pytest/vitest testing, Docker multi-stage builds, GitHub Actions CI/CD, PostgreSQL, TypeScript generics, Python async, and React Server Components.

    120 GitHub stars~1.2k tokensUpdated 7 mo ago
    DevOps & CloudAuto-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

Works with

Categories

Questions about Klaviyo CI Integration

What does Klaviyo CI Integration do?

Configure CI/CD pipelines for Klaviyo integrations with GitHub Actions. Klaviyo CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure CI/CD pipelines for Klaviyo integrations with GitHub Actions.

When should I use Klaviyo CI Integration?

Klaviyo CI Integration fits situations like: setting up automated testing; configuring CI secrets; integrating Klaviyo SDK tests into your build pipeline; with phrases like klaviyo CI.

How do I install Klaviyo CI Integration in Claude Code?

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

How do I install Klaviyo CI Integration in Codex?

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

Can I use Klaviyo CI Integration 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-ci-integration -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-ci-integration, .gemini/skills/klaviyo-ci-integration, .github/skills/klaviyo-ci-integration and .opencode/skills/klaviyo-ci-integration in your project.

What does Klaviyo CI Integration need to run?

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

Does Klaviyo CI Integration access the network?

SKILL.md names 1 domain. As links in the text: docs.github.com. This is read from the text; nothing was executed.

Is Klaviyo CI Integration 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 CI Integration use?

Klaviyo CI Integration 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 CI Integration use?

About 1.3k tokens (SKILL.md is roughly 5.1k 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.3k tokens, read only when the agent opens those files.

What are the alternatives to Klaviyo CI Integration?

Skills that share tags, products or a category with Klaviyo CI Integration: CI Failure Triage and Repair (Chachamaru127/claude-code-harness, 3.2k stars), CI Watchdog (latitude-dev/latitude-llm, 4.7k stars), Megatron-LM CI Failure Triage (NVIDIA/Megatron-LM, 18k stars) and CI Triage (fair-acc/gnuradio4, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Klaviyo CI Integration?

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.