Agent skill

Customerio Primary Workflow

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Implement Customer.io primary messaging workflow. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passedBackend & APIs

Install Customerio Primary Workflow

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill customerio-primary-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace customerio-primary-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/customerio-primary-workflow .claude/skills/customerio-primary-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
customerio-primary-workflow
GitHub stars
2.8k
Token cost
~2.3k tokens
SKILL.md length
377 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Implement Customer.io primary messaging workflow. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 4 steps: Define Your Event Taxonomy → Build the Messaging Service → Integrate into Application Routes → …
  • Setting up campaign triggers
  • SKILL.md covers Output, Examples, Overview and Prerequisites, plus 6 more sections
  • Needs CUSTOMERIO_TRACK_API_KEY

What it does

Customerio Primary Workflow is an agent skill from jeremylongshore/tons-of-skills-marketplace. Implement Customer.io primary messaging workflow. Use when setting up campaign triggers, welcome sequences, onboarding flows, or event-driven email automation. Trigger: "customer.io campaign", "customer.io workflow", "customer.io email automation", "customer.io messaging", "customer.io onboarding".

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Backend & APIs, covering Email management, Event-driven systems and Email marketing. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Setting up campaign triggers
  • Welcome sequences
  • Onboarding flows
  • Event-driven email automation

Example prompts

  • “customer.io campaign”
  • “customer.io workflow”
  • “customer.io email automation”
  • “/customerio-primary-workflow”

Requirements

  • A credential in CUSTOMERIO_TRACK_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Bash(npx:*), Glob, Grep

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Define Your Event Taxonomy
  2. Build the Messaging Service
  3. Integrate into Application Routes
  4. Dashboard Campaign Configuration

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(npm:*)
    • Bash(npx:*)
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.customer.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CUSTOMERIO_TRACK_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Customerio Primary Workflow loads about 2.3k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 377 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 377 words, ~2,271 tokens.

Download SKILL.mdSave it as .claude/skills/customerio-primary-workflow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
customerio-primary-workflow
description
Implement Customer.io primary messaging workflow. Use when setting up campaign triggers, welcome sequences, onboarding flows, or event-driven email automation. Trigger: "customer.io campaign", "customer.io workflow", "customer.io email automation", "customer.io messaging", "customer.io onboarding".
allowed-tools
Read, Write, Edit, Bash(npm:*), Bash(npx:*), Glob, Grep
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, customer-io, workflow, campaigns, automation

Customer.io Primary Workflow

Output

  • A consent-aware workflow with explicit trigger, audience, data contract, message/template version, and owner.
  • A synthetic validation receipt and a scoped rollback/disable action for unexpected delivery behavior.

Examples

Build the workflow in development using one synthetic profile and a versioned event, confirm trigger conditions and suppression/consent rules, then promote through staging. Enable production through an approved canary audience; pause/disable the workflow if the audience or message behavior does not match the reviewed expectation.

Overview

Implement Customer.io's core messaging workflow: identify users with segment-ready attributes, track lifecycle events that trigger campaigns, and set up the data layer for automated onboarding, nurture, and re-engagement sequences.

Prerequisites

  • customerio-node configured with Track API credentials
  • Campaigns created in Customer.io dashboard (triggered by events you define)
  • Understanding of your user lifecycle stages

How Campaigns Work

Your App (SDK)           Customer.io Dashboard          User
─────────────           ────────────────────          ────
cio.identify(user)  →   Profile created/updated
cio.track("signed_up")  →   Campaign trigger fires
                             Wait 1 day             →   Welcome email
                             Check: verified?
                             ├─ No                  →   Verification reminder
                             └─ Yes → Wait 3 days   →   Feature tips email

Events tracked via the SDK trigger campaigns you build in the dashboard. The SDK sends the data; the dashboard defines the workflow logic.

Instructions

Step 1: Define Your Event Taxonomy
typescript
// lib/customerio-events.ts
import { TrackClient, RegionUS } from "customerio-node";

// Central event definitions — every event your app tracks
export const CIO_EVENTS = {
  // Onboarding
  SIGNED_UP: "signed_up",
  EMAIL_VERIFIED: "email_verified",
  PROFILE_COMPLETED: "profile_completed",
  FIRST_PROJECT_CREATED: "first_project_created",

  // Engagement
  FEATURE_USED: "feature_used",
  INVITED_TEAMMATE: "invited_teammate",
  UPGRADE_STARTED: "upgrade_started",
  UPGRADE_COMPLETED: "upgrade_completed",

  // Lifecycle
  SUBSCRIPTION_RENEWED: "subscription_renewed",
  SUBSCRIPTION_CANCELLED: "subscription_cancelled",
  TRIAL_EXPIRING: "trial_expiring",

  // Commerce
  CHECKOUT_STARTED: "checkout_started",
  CHECKOUT_COMPLETED: "checkout_completed",
  REFUND_REQUESTED: "refund_requested",
} as const;

type EventName = (typeof CIO_EVENTS)[keyof typeof CIO_EVENTS];
Step 2: Build the Messaging Service
typescript
// services/customerio-messaging.ts
import { TrackClient, RegionUS } from "customerio-node";
import { CIO_EVENTS } from "../lib/customerio-events";

const cio = new TrackClient(
  process.env.CUSTOMERIO_SITE_ID!,
  process.env.CUSTOMERIO_TRACK_API_KEY!,
  { region: RegionUS }
);

interface UserProfile {
  id: string;
  email: string;
  firstName: string;
  lastName?: string;
  plan: string;
  companyName?: string;
}

export class MessagingService {
  /** Call on user signup — creates profile and triggers onboarding campaign */
  async onSignup(user: UserProfile, signupMethod: string): Promise<void> {
    // 1. Identify with all attributes campaigns need
    await cio.identify(user.id, {
      email: user.email,
      first_name: user.firstName,
      last_name: user.lastName ?? "",
      plan: user.plan,
      company: user.companyName ?? "",
      created_at: Math.floor(Date.now() / 1000),
      onboarding_step: "signed_up",
    });

    // 2. Track the event that triggers the onboarding campaign
    await cio.track(user.id, {
      name: CIO_EVENTS.SIGNED_UP,
      data: {
        method: signupMethod,  // "google", "email", "github"
        plan: user.plan,
      },
    });
  }

  /** Call when user verifies email — updates profile + tracks event */
  async onEmailVerified(userId: string): Promise<void> {
    await cio.identify(userId, {
      email_verified: true,
      email_verified_at: Math.floor(Date.now() / 1000),
      onboarding_step: "verified",
    });

    await cio.track(userId, {
      name: CIO_EVENTS.EMAIL_VERIFIED,
    });
  }

  /** Call on feature usage — drives engagement segments and campaigns */
  async onFeatureUsed(
    userId: string,
    feature: string,
    metadata?: Record<string, any>
  ): Promise<void> {
    await cio.track(userId, {
      name: CIO_EVENTS.FEATURE_USED,
      data: { feature, ...metadata },
    });

    // Update engagement metrics on the profile for segmentation
    await cio.identify(userId, {
      last_active_at: Math.floor(Date.now() / 1000),
    });
  }

  /** Call on plan upgrade — triggers upgrade confirmation campaign */
  async onUpgrade(userId: string, from: string, to: string, mrr: number): Promise<void> {
    await cio.identify(userId, {
      plan: to,
      mrr,
      upgraded_at: Math.floor(Date.now() / 1000),
    });

    await cio.track(userId, {
      name: CIO_EVENTS.UPGRADE_COMPLETED,
      data: { from_plan: from, to_plan: to, mrr },
    });
  }

  /** Call on cancellation — triggers win-back campaign */
  async onCancellation(userId: string, reason: string): Promise<void> {
    await cio.identify(userId, {
      plan: "cancelled",
      cancelled_at: Math.floor(Date.now() / 1000),
      cancellation_reason: reason,
    });

    await cio.track(userId, {
      name: CIO_EVENTS.SUBSCRIPTION_CANCELLED,
      data: { reason },
    });
  }
}
Step 3: Integrate into Application Routes
typescript
// routes/auth.ts (Express example)
import { MessagingService } from "../services/customerio-messaging";

const messaging = new MessagingService();

router.post("/signup", async (req, res) => {
  const user = await db.createUser(req.body);

  // Fire-and-forget — don't block the signup response
  messaging.onSignup(
    {
      id: user.id,
      email: user.email,
      firstName: user.firstName,
      plan: user.plan,
    },
    req.body.signupMethod
  ).catch((err) => console.error("CIO signup tracking failed:", err));

  res.json({ user });
});

router.post("/verify-email", async (req, res) => {
  await db.verifyEmail(req.user.id);
  messaging.onEmailVerified(req.user.id).catch(console.error);
  res.json({ verified: true });
});
Show full SKILL.md (203 more words)Show less
Step 4: Dashboard Campaign Configuration

In Customer.io dashboard, create campaigns triggered by these events:

Onboarding Campaign:

  1. Trigger: Event signed_up
  2. Wait 5 minutes
  3. Send welcome email (use {{ customer.first_name }} and {{ event.method }} Liquid)
  4. Wait 1 day
  5. Branch: Is email_verified true?
    • No → Send verification reminder
    • Yes → Continue
  6. Wait 3 days
  7. Send feature tips email
  8. Wait 7 days
  9. Branch: Has first_project_created event?
    • No → Send activation nudge
    • Yes → End (move to engagement campaign)

Cancellation Win-back Campaign:

  1. Trigger: Event subscription_cancelled
  2. Wait 3 days
  3. Send "We miss you" email with {{ event.reason }} Liquid variable
  4. Wait 7 days
  5. Send discount offer email

Liquid Template Variables

VariableSourceExample
{{ customer.first_name }}identify() attributes"Jane"
{{ customer.plan }}identify() attributes"pro"
{{ event.method }}track() event data"google"
{{ event.reason }}track() event data"too_expensive"

Error Handling

ErrorCauseSolution
Campaign not triggeringEvent name mismatchEvent names are case-sensitive — verify exact match
User not receiving emailMissing email attributeAlways include email in identify()
Duplicate sendsMultiple event firesUse fire-and-forget with deduplication
Liquid rendering {{ }}Missing data propertyEnsure data object has all template variables

Resources

Next Steps

After implementing primary workflow, proceed to customerio-core-feature for transactional messages, segments, and broadcasts.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/customerio-primary-workflow of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Customerio Primary Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Customerio Primary Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Customerio Primary Workflow this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.3kAutomated safety check: PassMIT
Abp Microserviceabpframework/abp14k—~1.7kAutomated safety check: PassLGPL-3.0
Amq CLIhashgraph-online/awesome-codex-plugins1.3k—~1.9kAutomated safety check: PassApache-2.0
Backend Engineeringmagnus919/agent-skills115—~2.6kAutomated safety check: PassMIT
Flow Nexus Swarmruvnet/agentic-flow8174 repos~4.2kAutomated safety check: PassNone
Email Deliverability Auditgrowthenginenowoslawski/coldoutboundskills753—~3.4kAutomated safety check: PassMIT

Similar skills

  • Abp Microservice

    abpframework/abp

    ABP Microservice solution template - service structure, Integration Services ([IntegrationService]), inter-service HTTP proxies, distributed events with Outbox/Inbox, Entity Cache…

    14k GitHub stars~1.7k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Amq CLI

    hashgraph-online/awesome-codex-plugins

    Coordinate coding agents through AMQ. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~1.9k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Backend Engineering

    magnus919/agent-skills

    Design and implement backend services and APIs — REST, gRPC, GraphQL, event-driven handlers, transaction boundaries, outbox/inbox delivery, migration coexistence, database access, integration, error…

    115 GitHub stars~2.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Flow Nexus Swarm

    ruvnet/agentic-flow

    Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform

    817 GitHub starsUsed in 4 repos~4.2k tokens
    Backend & APIsAuto-check passed
  • Email Deliverability Audit

    growthenginenowoslawski/coldoutboundskills

    Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.

    753 GitHub stars~3.4k tokensUpdated 5 days ago
    Backend & APIsAuto-check passed
  • Aqua Communication

    quailyquaily/aqua

    Aqua is a CLI-first message tool for AI agents. An agent skill from quailyquaily/aqua.

    258 GitHub stars~4.7k tokensUpdated 6 mo ago
    Backend & APIsAuto-check: notes

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Customerio Primary Workflow

What does Customerio Primary Workflow do?

Implement Customer.io primary messaging workflow. An agent skill from jeremylongshore/tons-of-skills-marketplace. Customerio Primary Workflow is an agent skill from jeremylongshore/tons-of-skills-marketplace.io primary messaging workflow.

When should I use Customerio Primary Workflow?

Customerio Primary Workflow fits situations like: setting up campaign triggers; welcome sequences; onboarding flows; event-driven email automation.

How do I install Customerio Primary Workflow in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill customerio-primary-workflow -a claude-code`. Or copy the skill folder (skills/.curated/customerio-primary-workflow in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/customerio-primary-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Customerio Primary Workflow in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill customerio-primary-workflow -a codex`. Or copy the skill folder (skills/.curated/customerio-primary-workflow in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/customerio-primary-workflow in your project. Codex loads it when a task matches its description.

Can I use Customerio Primary Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill customerio-primary-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customerio-primary-workflow, .gemini/skills/customerio-primary-workflow, .github/skills/customerio-primary-workflow and .opencode/skills/customerio-primary-workflow in your project.

What does Customerio Primary Workflow need to run?

Going by SKILL.md and its folder, Customerio Primary Workflow needs credentials named CUSTOMERIO_TRACK_API_KEY. Our summary lists: A credential in CUSTOMERIO_TRACK_API_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*), Bash(npx:*), Glob, Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Customerio Primary Workflow access the network?

SKILL.md names 1 domain. As links in the text: docs.customer.io. This is read from the text; nothing was executed.

Is Customerio Primary Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Customerio Primary Workflow use?

Customerio Primary Workflow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Customerio Primary Workflow use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Customerio Primary Workflow?

Skills that share tags, products or a category with Customerio Primary Workflow: Abp Microservice (abpframework/abp, 14k stars), Amq CLI (hashgraph-online/awesome-codex-plugins, 1.3k stars), Backend Engineering (magnus919/agent-skills, 115 stars) and Flow Nexus Swarm (ruvnet/agentic-flow, 817 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Customerio Primary Workflow?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.