Agent skill · software engineering · jeremylongshore
customerio-deploy-pipeline
Deploy Customer.io integrations to production cloud platforms.
Why this skill is useful
Adds deployment scripts and health check implementations for Customer.io integrations across multiple cloud platforms, which are not commonly found in public documentation.
What it needs
Requires gcloud, kubectl, npm 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 Deploy Pipeline Output A versioned, staged deployment of Customer.io configuration/code with owner approval, validation evidence, and a rollback reference. A protected promotion path that prevents unreviewed changes from affecting production recipients. Examples Validate an event/template configuration in development and staging with synthetic profiles, attach schema/template test results to the change, then release through an approved canary. If the canary shows wrong audience, consent, or rendering behavior, stop promotion and restore the last approved configuration. Overview Deploy Customer.io integrations to production: GCP Cloud Run with Secret Manager, Vercel serverless functions, AWS Lambda with SSM, Kubernetes with external secrets, plus health check endpoints and blue-green deployment scripts. Prerequisites CI/CD pipeline configured (see customerio-ci-integration) Cloud platform credentials and access Production Customer.io credentials in a secrets manager Instructions Step 1: Deploy to Google Cloud Run Step 2: Health Check Endpoint Step 3: Vercel Serverless Functions Step 4: Kubernetes Deployment Step 5: Blue-Green Deployment Deployment Checklist [ ] Production secrets in secrets manager (not env files) [ ] Health check endpoint responds 200 [ ] Readiness and liveness probes configured [ ] Resource limits set (CPU, memory) [ ] Min instances > 0 (avoid cold starts) [ ] Blue-green or canary deployment configured [ ] Rollback procedure documented [ ] Post-deploy smoke test automated Error Handling Issue Solution ------- ---------- Secret not found Verify secret name in secrets manager Health check timeout Increase initialDelaySeconds, check CIO connectivity Cold start latency Set --min-instances 1 (Cloud Run) or keep-alive Memory OOM Increase memory limits, check for event queue buildup Resources Cloud Run Documentation Vercel Serverless Functions Kubernetes Secrets Next Steps After deployment, proceed to customerio-webhooks-events for webhook han …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-deploy-pipeline