customerio-install-auth
Install and configure Customer.io SDK/CLI authentication. Use when setting up a new Customer.io integration, configuring API keys, or initializing Customer.io in your project. "configure customer.io API key", "customer.io credentials". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-install-auth --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 Install & Auth ## Overview Set up the `customerio-node` SDK and configure authentication for Customer.io's two API surfaces: the **Track API** (identify users, track events) and the **App API** (transactional messages, broadcasts, data queries). ## Prerequisites - Node.js 18+ with npm/pnpm - Customer.io account at https://fly.customer.io - **Site ID** + **Track API Key** from Setting
What does the customerio-install-auth skill do?
Install and configure Customer.io SDK/CLI authentication. Use when setting up a new Customer.io integration, configuring API keys, or initializing Customer.io in your project. "configure customer.io API key", "customer.io credentials". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-install-auth --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.
