customerio-debug-bundle
Collect Customer.io debug evidence for support tickets. Use when creating support requests, investigating delivery failures, or documenting integration issues. "collect customer.io logs", "customer.io diagnostics". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-debug-bundle --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Customer.io Debug Bundle ## 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 supp
What does the customerio-debug-bundle skill do?
Collect Customer.io debug evidence for support tickets. Use when creating support requests, investigating delivery failures, or documenting integration issues. "collect customer.io logs", "customer.io diagnostics". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-debug-bundle --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
