customerio-cost-tuning
Optimize Customer.io costs and usage efficiency. Use when reducing profile count, cleaning inactive users, deduplicating events, or right-sizing your plan. "customer.io billing", "customer.io pricing", "customer.io cleanup". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-cost-tuning --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 Cost Tuning ## Overview Optimize Customer.io costs by managing profile count (the primary billing driver), suppressing/deleting inactive users, deduplicating events, reducing unnecessary API calls, and monitoring usage trends. ## How Customer.io Pricing Works Customer.io bills based on **profile count** (number of identified people in your workspace) and **email/SMS volume**. Key cos
What does the customerio-cost-tuning skill do?
Optimize Customer.io costs and usage efficiency. Use when reducing profile count, cleaning inactive users, deduplicating events, or right-sizing your plan. "customer.io billing", "customer.io pricing", "customer.io cleanup". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-cost-tuning --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.
