Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/klaviyo-ci-integration
Configure CI/CD pipelines for Klaviyo integrations with GitHub Actions.
Passed 20 of 22 test cases with the skill, and 9 of 22 without it.
and 24 more in the full report
11 fixed9 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
After setting up CI testing for Klaviyo integrations using GitHub Actions, a developer asked about deployment workflows. What specific complementary skill or pattern in this pack covers downstream deployment automation?
| Checked | Without skill | With skill |
|---|---|---|
| References klaviyo-deploy-integration skill. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
klaviyo-api SDK and Vitest configured in the repositoryStore the Klaviyo test credentials as encrypted repository secrets:
gh secret set KLAVIYO_PRIVATE_KEY --body "pk_test_***"
gh secret set KLAVIYO_WEBHOOK_SIGNING_SECRET --body "whsec_test_***"
Create .github/workflows/klaviyo-ci.yml with two jobs. The essential skeleton:
name: Klaviyo Integration CI
on:
push:
branches: [main]
pull_request:
branches: [main]
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.