Agent skill · marketing growth · aiskillstore
sequenzy-email-marketing
Primary agent guide for operating Sequenzy as an email-marketing platform. Use when Codex needs to authenticate, inspect identity, manage subscribers, create or edit campaigns/sequences/templates, control the campaign lifecycle (cancel, pause, resume, delete, duplicate), run campaign A/B tests, mutate lists/tags/segments, enroll subscribers into sequences, invite team members, triage and reply to inbox conversations, manage outbound webhooks, generate draft email content, send transactional email, read delivery stats, or decide whether a requested Sequenzy email-marketing workflow is currently supported. Prefer this over the generic sequenzy skill when both seem relevant.
Why this skill is useful
Adds detailed workflows and CLI commands for managing email marketing campaigns that are not publicly documented.
What it needs
Requires sequenzy account access. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Sequenzy Email Marketing Overview Use this as the default skill for Sequenzy email-marketing/product operations: subscribers, lists, tags, segments, campaigns, sequences, templates, AI email generation, transactional sends, delivery stats, dashboard URLs, CLI/MCP behavior, and currently-supported workflow checks. Prefer the sequenzy CLI for supported workflows, treat packages/mcp/src/tools/index.ts as the MCP source of truth when the task goes through MCP tools, and explicitly call out when a requested workflow is not wired in the current implementation. If both sequenzy and sequenzy-email-marketing match, load this skill first. Ground Rules 1. Treat packages/cli/src/index.tsx as the source of truth for which commands are actually wired. 2. Treat packages/cli/src/commands/ and packages/cli/src/api.ts as the source of truth for CLI behavior, payload shape, and API routes. 3. Treat packages/mcp/src/tools/index.ts as the source of truth for MCP tool names, arguments, and preflight validation. 4. Do not promise support for commands or tools that only appear in docs or --help text without an attached implementation. 5. Prefer sequenzy login for interactive auth and SEQUENZYAPIKEY for automation. 6. Prefer inspection before mutation whenever the workflow allows it. Supported Workflows Read references/use-cases.md before executing anything non-trivial. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/sequenzy-email-marketing