Agent skill · software engineering · jeremylongshore
customerio-local-dev-loop
Configure Customer.io local development workflow.
Why this skill is useful
Provides specific configuration patterns and a mock client implementation for testing Customer.io that the AI wouldn't reliably generate on its own.
What it needs
Requires customerio-node, dotenv installed locally. Requires customer.io 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 Local Dev Loop Output A small, test-backed local change using a non-production workspace and synthetic recipient data. A reviewed deployment/revert path that preserves production campaigns, consent, and contact data. Examples Use a development workspace and a synthetic profile such as test-user-001; validate the event schema locally, run the focused test, and inspect the resulting campaign behavior before committing. Never point local experiments at production segments or use real recipient data to debug a template. Overview Set up an efficient local development workflow for Customer.io: environment isolation via separate workspaces, a dry-run client for safe development, test mocks for unit tests, and prefixed events that never pollute production data. Prerequisites customerio-node installed Separate Customer.io workspace for development (recommended — free workspaces available) dotenv or similar for environment variable loading Instructions Step 1: Environment Configuration Step 2: Environment-Aware Client Step 3: Test Mocks for Unit Tests Step 4: Integration Test with Real API Run integration tests only against your dev workspace: Step 5: Dev Scripts Workspace Isolation Strategy Environment Workspace Name Event Prefix Dry Run ------------- --------------- -------------- --------- Unit tests (mocked) test true Integration tests myapp-dev inttest false Staging myapp-staging (none) false Production myapp-prod (none) false Error Handling Error Cause Solution ------- ------- ---------- Dev events in production Wrong .env file loaded Verify NODEENV and env file path Mock not intercepting Import order issue Mock customerio-node before importing your client module Test user pollution No cleanup Always suppress + destroy test users in afterAll Resources Customer.io Workspaces customerio-node GitHub Next Steps After setting up local dev, proceed to customerio-sdk-patterns for production-ready patterns.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-local-dev-loop--ea6bf0