Agent skill · software engineering · jeremylongshore
customerio-ci-integration
Configure Customer.io CI/CD integration with automated testing.
Why this skill is useful
Adds a complete CI/CD pipeline setup for Customer.io with executable scripts and specific testing patterns not commonly found in public documentation.
What it needs
Requires node, npm installed locally. Requires customer.io, github account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Customer.io CI Integration Output A credential-free pull-request lane for schema/template/unit checks and a trusted scoped lane for optional integration tests. A redacted CI receipt with validation results and a safe failure/retry procedure. Examples Run event-schema and template tests on every pull request using fixtures, then execute a single synthetic integration event only from a protected branch with a development workspace secret. If a live check fails, retain redacted status and back off; never expose workspace credentials to forked code or bypass protected checks. Overview Set up CI/CD pipelines for Customer.io integrations: GitHub Actions workflow with unit + integration tests, test fixtures with automatic cleanup, pre-commit hooks, and environment-specific credential management. Prerequisites GitHub repository with Node.js project Separate Customer.io workspace for CI testing (do NOT use production) GitHub Actions secrets configured Instructions Step 1: GitHub Actions Workflow Step 2: Test Fixtures and Helpers Step 3: Integration Test Suite Step 4: Test User Cleanup Script Step 5: GitHub Secrets Setup Step 6: Pre-commit Hook CI Best Practices Practice Rationale ---------- ----------- Dedicated test workspace Prevents CI from polluting dev/staging data Unique test user IDs Prevents collisions between parallel CI runs Always cleanup in afterAll Prevents accumulating stale test profiles Rate limit awareness Add small delays between batched API calls in CI Skip integration tests if no creds PRs from forks won't have secrets Error Handling Issue Solution ------- ---------- Secrets not available in PR Fork PRs don't get secrets — skip integration tests gracefully Test user pollution Use ${TESTRUNID} prefix, cleanup in afterAll Rate limiting in CI Keep integration test count under 50 API calls Flaky network failures Add retry logic to integration tests Resources GitHub Actions Encrypted Secrets vitest Documentation Next Steps After CI setup, proceed to customerio …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-ci-integration