skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
customerio/cli320 installs

cio

Customer.io CLI - use for Customer.io, Journeys, CDP Pipelines, new-account onboarding and signup, app integration, SDK setup, message design, message automation (automations, broadcasts, transactional messages), plans and billing, service account tokens, sources, destinations, identify/track events, and fly.customer.io / cdp.customer.io errors. Trigger even when the user does not name the CLI.

How do I install this agent skill?

npx skills add https://github.com/customerio/cli --skill cio
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill acts as a bootstrap for the Customer.io CLI (cio). It provides commands to initialize the CLI, fetch installation instructions from the official repository, and read service-specific documentation. No malicious patterns or security risks were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Customer.io (cio)

This is the installable bootstrap skill for agents using the Customer.io CLI. Run cio prime first; it prints the compact CLI reference, JSON output rules, command syntax, schema introspection, pagination, error shapes, and skill-reading guidance.

cio prime

If the user has no Customer.io account, create one with cio auth signup. cio prime explains the flow.

If cio is not installed, install it with npm:

npm install -g @customerio/cli

Use runtime references instead of copying large playbooks into this skill:

  • cio schema for commands, flags, generic API routes, and payload shapes.
  • cio skills to list currently available Customer.io reference skills.
  • cio skills read cio for skills unique to the CLI (auth/login, integration, onboarding/new user setup); read it for the full index.
  • cio skills read <skill> for the specific service-hosted reference needed.
  • cio api <path> for API coverage that is not wrapped by a bespoke command.

Common routing:

  • New-account setup, signup and login, first app integration, and plan or billing questions start with cio prime and cio skills read cio.
  • Existing Journeys resources such as campaigns, segments, templates, customers, newsletters, and subscription topics should use cio skills read fly-api.
  • CDP Pipelines, sources, destinations, identify, track, page, and screen work should use cio skills read cdp-api.
  • Design Studio email/component editing should use cio skills read design-studio.
  • Analysis workflows, campaign review, goal-based segments, and Liquid should use cio skills read recipes.

Credential rule:

  • Service account tokens (sa_live_...) authenticate the CLI and account-level management operations.
  • Do not embed service account tokens in customer application code.
  • Use CDP source write keys for SDK identify/track/page/screen ingestion.
  • Use workspace-scoped App API keys for backend transactional sends.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/customerio/cli/cio">View cio on skillZs</a>