customerio-pipelines
Customer.io Data Pipelines (CDP). Use when the user wants to add or inspect sources, destinations, reverse ETL, database syncs, identify/track/page/screen calls, or data in/out integrations (Salesforce, HubSpot, Segment, warehouses, ad audiences). Triggers: "add a JavaScript source", "Pipelines", "CDP", "destination", "reverse ETL", "identify and track", "send data to Salesforce".
Install
With your agent
Install OMGSkills skill "customerio/claude-plugin:skills/customerio-pipelines" 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-pipelines ~/.claude/skills/customerio-pipelinesFrom README
Customer.io Pipelines Use this skill for Data Pipelines and integration routing. Confirm the Customer.io MCP server customerio is connected. Call cioprime. Read the live CDP skill — it is the entry point for integration questions: cioskillsread with path cdp-api Then the matching subfile, for example cdp-api/sources.md, cdp-api/destinations.md, cdp-api/reverseetl.md, cdp-api/journeysintegrations.md. Prefer a native Pipelines source for ongoing data in. Do not lead with a Track API or Zapier workaround. Discover endpoints with cioschema. Mutate with dryrun: true first. Automations, profiles, and segments are Journeys (customerio-journeys / fly-api). App SDK snippets are customerio-sdk / cio.