Versioned AI-agent skills for operating Sequenzy email marketing workflows from Claude Code, Codex, Hermes, and other SKILL.md-compatible agents.

Agents are increasingly asked to do real lifecycle marketing work, not just draft copy. This repo gives them a precise operating guide for Sequenzy so they can inspect account state, manage subscribers and segments, create campaigns or sequences and control their lifecycle (cancel, pause, resume), run A/B tests, enroll subscribers, invite teammates, triage inbox replies, manage outbound webhooks, generate email drafts, send transactional emails, and surface review URLs without guessing command names or API payloads.

The installable skills are:

• sequenzy-email-marketing: primary skill for operating campaigns and their lifecycle (cancel, pause, resume, delete, duplicate), A/B tests, sequences and manual enrollment, subscribers, lists, tags, segments, templates, team members, inbox conversations, outbound webhooks, transactional sends, stats, websites, and API keys through Sequenzy's CLI/API surface.
• sequenzy: concise compatibility alias for broad Sequenzy references; use the explicit email-marketing skill when both apply.

Install the explicit email-marketing skill from GitHub:

npx skills add Sequenzy/skills --skill sequenzy-email-marketing

Or install the concise compatibility alias:

npx skills add Sequenzy/skills --skill sequenzy

Install for a specific agent when your skills CLI supports agent adapters:

# Claude Code
npx skills add Sequenzy/skills --skill sequenzy-email-marketing -a claude-code -y

# OpenAI Codex
npx skills add Sequenzy/skills --skill sequenzy-email-marketing -a codex -y

# Local checkout / development
npx skills add . --skill sequenzy-email-marketing -a codex -y

Hermes users can copy or sync the skill into their Hermes skills directory, then load it by name:

hermes skills list | grep sequenzy-email-marketing

1. Load skills/sequenzy-email-marketing/SKILL.md.
2. Read references/use-cases.md before non-trivial mutations.
3. Authenticate with either:

sequenzy login
# or, for automation
export SEQUENZY_API_KEY=...

4. Verify access before mutating anything:

sequenzy whoami
sequenzy account

Use Sequenzy to draft a 4-email onboarding sequence for new trial users, then give me the dashboard URL to review it.

Check last 30 days campaign stats, identify the weakest campaign, and suggest subject-line improvements without sending anything.

Add user@example.com as a subscriber with the tags beta and founder, then show the saved subscriber profile.

Create a saved segment for users who purchased Pro at least 3 times and preview its count before we use it in a campaign.

The April launch campaign was scheduled with the wrong date - cancel it, fix the schedule, and give me the review URL.

Triage unread inbox replies: summarize each open conversation, reply to the simple ones, and leave internal notes on anything that needs my input.

This repo includes a machine-readable discovery file at .well-known/skills/index.json. Catalogs and agents can use it to find the canonical skill path, compatibility notes, and install command.

.well-known/skills/index.json
skills/
  sequenzy/
    SKILL.md
    agents/openai.yaml
    references/
  sequenzy-email-marketing/
    SKILL.md
    agents/openai.yaml
    references/
      command-reference.md
      use-cases.md

Keep the installable skill inside skills/<skill-name>/ and treat SKILL.md as the source of truth for triggers, supported workflows, caveats, and verification steps. Reference files should contain longer command examples and decision trees so the main skill stays readable.

When adding a new skill, also update .well-known/skills/index.json so catalogs can discover it.