customerio-journeys
Customer.io Journeys. Use when the user wants to create, list, edit, or review automations, campaigns, broadcasts, one-time sends, profiles, people, customers, segments, newsletters, subscription topics, transactional messages, or in-app messages. Triggers: "list automations", "create a campaign", "win-back segment", "people who haven't opened", "find profiles", "transactional send", "in-app message".
Install
With your agent
Install OMGSkills skill "customerio/claude-plugin:skills/customerio-journeys" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/customerio/claude-plugin /tmp/claude-plugin && ln -s /tmp/claude-plugin/skills/customerio-journeys ~/.claude/skills/customerio-journeysFrom README
Customer.io Journeys Use this skill for workspace messaging and audience work in Journeys. Confirm the Customer.io MCP server customerio is connected. Call cioprime. Read the live Journeys skill — do not guess workflow details: cioskillsread with path fly-api Then the matching subfile, for example: Automations / campaigns → fly-api/automations.md (also triggers, filters, lifecycle, review) Profiles / people → fly-api/customers.md Segments → fly-api/segments.md, fly-api/datadrivensegments.md, fly-api/segmentconditions.md Messaging / newsletters / transactional / in-app → fly-api/messaging.md, fly-api/transactionalsend.md, fly-api/inapp.md Discover the endpoint with cioschema (for example campaigns or campaigns.create). GET with cioreadapi. Mutate with ciowriteapi or ciodeleteapi and dryrun: true first. Email content in Design Studio is not this skill — use customerio-design-studio (design-studio). Data sources and destinations are customerio-pipelines (cdp-api).