Agent skill · data analytics · jeremylongshore
customerio-debug-bundle
Collect Customer.io debug evidence for support tickets.
Why this skill is useful
Adds a comprehensive debug script for diagnosing Customer.io issues that includes API connectivity tests and user profile investigations.
What it needs
Requires curl 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 Debug Bundle Output A minimal redacted diagnostic bundle containing correlation IDs, environment, timestamps, configuration version, and status/error class. An incident disposition that protects recipient data and credentials while allowing reproduction or vendor escalation. Examples For a delivery failure, collect the opaque event/message correlation ID, workspace, timestamp, template/workflow version, and redacted status. Do not export email addresses, full payloads, tokens, or message content. Reproduce with a synthetic profile, then share only the approved redacted bundle with support. Current State !node --version 2>/dev/null echo 'Node.js: not installed' !npm list customerio-node 2>/dev/null grep customerio echo 'customerio-node: not installed' Overview Collect a comprehensive debug bundle for Customer.io support tickets: API connectivity tests, user profile inspection, SDK version info, environment validation, and a structured support report. Prerequisites Customer.io API credentials configured curl available for API tests User ID or email of the affected user/delivery Instructions Step 1: API Connectivity Diagnostic Step 2: User Profile Investigation Step 3: SDK and Environment Info Step 4: Generate Support Report Step 5: Collect Application Logs Debug Checklist [ ] Customer.io status page checked (https://status.customer.io) [ ] Track API auth verified (HTTP 200) [ ] App API auth verified (HTTP 200) [ ] User profile exists and has email attribute [ ] User is not suppressed [ ] SDK version documented [ ] Region configuration correct (US vs EU) [ ] Error logs collected and redacted [ ] Reproduction steps documented Error Handling Issue Solution ------- ---------- Status page unreachable Check your network; try from a different network Both APIs return 401 Credentials are wrong — regenerate in dashboard Track OK but App 401 Using Track API key for App API — they're separate keys Logs contain PII Run redaction script before sharing with support Reso …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-debug-bundle--a6b105