Coding

Sequenzy

Try it

Routes broad Sequenzy requests to the right command, tool, or feedback path so agents stop promising unsupported actions.

What it does

Generic entry point for Sequenzy tasks when no narrower skill obviously fits; defers email-marketing/product work to sequenzy-email-marketing. It checks every recommendation against the CLI command tree and the MCP tool registry before answering, so workflows that are not actually wired are not claimed as supported. When a request is unsupported, it surfaces the gap, points to the dashboard or direct API as the next-best path, and routes it through `sequenzy feedback` so the Sequenzy team can see it.

When to use it

  • User mentions Sequenzy with no specific task — pick the right skill or fallback command
  • Agent needs to verify a CLI or MCP command exists before recommending it
  • Requested workflow turns out to be unsupported — report the gap and suggest the dashboard or API
  • Auth method is unclear — choose between `sequenzy login` and `SEQUENZY_API_KEY`

The skill document

Sequenzy

Overview

Use this generic skill when the user refers broadly to Sequenzy and no narrower skill is obviously better. For email-marketing/product work, prioritize sequenzy-email-marketing: campaigns, subscribers, lists, tags, segments, templates, sequences, transactional email, 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.

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 SEQUENZY_API_KEY for automation.
  6. Prefer inspection before mutation whenever the workflow allows it.

Supported Workflows

Read references/use-cases.md before executing anything non-trivial. The currently implemented CLI flows are:

  • login and logout
  • local auth/session check with whoami
  • account inspection with account
  • company inspection, creation, or brand/sender-identity updates with companies list|get|create|update
  • stats overview or stats by campaign, sequence, or transactional ID, with custom --start/--end ranges, --email-type and --mailbox-provider scoping, --include-bots, and campaign clickedLinks plus poll/NPS polls arrays
  • raw delivery/engagement event listing with events --campaign|--sequence, and per-delivery inspection with email-sends list|get plus bounce-suppression cleanup with suppressions get|remove
  • subscribers list, add, update, get, and remove, with list fetching every page by default and supporting tag, segment, and list filters; add and update set native profile names via --first-name / --last-name (MCP add_subscriber / update_subscriber: firstName / lastName), so never store names in custom attributes; both also handle native phone numbers and SMS consent
  • bulk subscriber imports with subscribers import / import-status, subscriber notes, custom event triggering with subscribers event (live or --occurred-at backfill), and bulk tag operations with subscribers tags add|remove
  • lists list, create, update, delete, add-subscribers, remove-subscribers, and import alias for bulk list population from emails, JSON, CSV, or newline files
  • tags list, create, update, and delete, with bare sequenzy tags still listing tag definitions for backwards compatibility
  • segments list, create, update, delete, and count, including --match any, nested filter roots, custom event filters, and saved-segment composition filters
  • templates list, get, create, update, and delete, with list supporting label filters and create/update accepting labels, raw HTML, or Sequenzy block JSON
  • campaigns list, get, create, update including label and reply-to updates, schedule, and test, with list supporting label filters, create accepting labels plus raw HTML, Sequenzy block JSON, or prompt-generated content, update accepting labels plus raw HTML or Sequenzy block JSON, and schedule returning a review preview link; create and schedule both accept the audience via --segment or --target-lists-json/--target-lists-file
  • campaign lifecycle control with campaigns cancel (stops scheduled, paused, waiting-approval, or sending campaigns immediately, no confirmation prompt), campaigns unschedule (returns a scheduled campaign or recurring series to draft), campaigns pause and campaigns resume for an active send (resume supports --spread-over-hours), campaigns delete (blocked while sending, scheduled, or paused - cancel first), and campaigns duplicate with --mode campaign|ab_test|variant
  • campaign audience inspection with campaigns audience, true-to-send HTML previews with campaigns render / templates render / sequences render (subscriber or ad-hoc personalization, locale, tracking, --out), recurring sends with campaigns schedule --repeat weekly|monthly, and post-send re-engagement with campaigns resend-to-non-openers
  • ab-tests list, get, stats, restart, update-variant, create, add-variant, delete-variant, and delete; create/add-variant/delete-variant/delete work on campaign A/B tests in draft status, variant A is the protected control, and restart reruns a finished sequence A/B test
  • MCP template and campaign tools support labels on list/create/update; MCP update_campaign also supports replyTo and replyProfileId, and MCP schedule_campaign schedules draft or already scheduled campaigns
  • MCP search_subscribers supports list filters through list, listId, or listName; MCP add_subscribers_to_list accepts up to 500 emails per call
  • sequences list, get, create, update, enable, disable, delete, enroll, and cancel-enrollments, including explicit discount action steps, cancellation by subscriber ID or event-property field values, and update branch insertion with tag, list, segment, event, clicked-link, and field conditions; event and clicked-link branch checks can use activityScope (this_sequence, previous_email, ever)
  • manual sequence enrollment with sequences enroll from emails, JSON, or files, optionally at a specific node with --target-node-id, reporting enrolled, skipped, and not-found subscribers
  • team list, invite with --role admin|viewer and owner-only --billing-access, and cancel-invitation
  • inbox list with status, search, unread, and pagination filters, get, reply including internal notes with --note, close, reopen, and mark-read
  • webhooks list, create, update, delete, test, deliveries, and replay for outbound webhook endpoints, with create printing the signing secret exactly once
  • AI generation with generate email, generate sequence, generate subjects, and generate sms
  • dashboard URL generation with CLI urls, MCP get_app_urls, and appUrls/url fields on campaign, sequence, template, and company results
  • websites list, add, check, and guide
  • products list, sync, upsert (API-provider products keyed by your own ID, bulk up to 100), delete, attach-file, and detach-file for digital product delivery, with attach-file --file uploading local files via presigned URLs; attached files are exposed on saas.purchase events as {{event.download.url}} / {{event.download.name}} (MCP: list_products, upsert_products, delete_product, attach_product_file, remove_product_file, sync_products)
  • API key management with api-keys create|list|revoke, including permission presets and explicit scopes on create
  • transactional email: one-off sends by template or raw HTML with send, plus saved-template management with transactional list|get|create|update|delete and preferences-iframe tokens via transactional widgets preferences-token
  • forms list and update (MCP additionally: create_form, get_form_embed) and full landing-page management with landing-pages including publish/unpublish, duplicate, custom domains, and DNS verification
  • sequence operations beyond CRUD: render, per-node test sends, duplicate, archive/unarchive, enrollment listing with CSV export, pause-enrollments/resume-enrollments, conversion goals, and inbound trigger webhook get|configure|rotate
  • template AI/manual localization with templates localizations set|sync
  • integrations: catalog, connect (API-key/webhook-secret providers; OAuth providers connect in the dashboard), list, get, activity, sync, enable-sync/disable-sync, Shopify pixel/enable-pixel, and guide
  • Meta Ads audience syncs with audience-syncs list|ad-accounts|create|update|delete|sync
  • deliverability and sending config: sender-profiles list|update, tracking settings|update (open/click tracking, strict bot filtering, attribution window, double opt-in, auto-UTM), and sequence/step-level sending windows
  • Shopify automation settings with shopify settings get|update (browse abandonment, cart abandonment, price drop)
  • SMS operations with sms settings, sms send-test, SMS sequence steps, and generate sms
  • integration event-to-tag sync rules with sync-rules get|update
  • personal notification preferences with account notifications get|set
  • product feedback with feedback, sending missing-capability reports, bug reports, and other product feedback straight to the Sequenzy team (MCP: submit_feedback)

Unsupported Or Placeholder Workflows

Treat missing subcommands as unsupported even when the noun exists. The main remaining gaps: campaign immediate send (no "send now" command - schedule with a near-future --at timestamp instead), sending domain add/verify (MCP add_sending_domain / verify_sending_domain or dashboard only), form creation and embed snippets (MCP create_form / get_form_embed only), and image asset upload (MCP upload_image_asset only). Bulk list population is supported through sequenzy lists add-subscribers and its sequenzy lists import alias, not through subscribers add. Whenever the user wanted something unsupported, report the gap with sequenzy feedback "..." --category missing_capability (MCP: submit_feedback) so it reaches the Sequenzy team.

Execution Pattern

  1. Check auth first with sequenzy whoami or by verifying SEQUENZY_API_KEY is set.
  2. Pick the narrowest command that matches the use case.
  3. Validate IDs, recipient email, subject, template, or content input before issuing a mutation.
  4. Surface CLI limitations directly instead of inventing a workaround.
  5. If the workflow is unsupported in the CLI, say whether the next-best path is the Sequenzy dashboard or direct API use, and report the gap with sequenzy feedback "..." --category missing_capability (MCP: submit_feedback).
  6. When you create, inspect, or schedule a campaign, sequence, template, or company and the user may want to review/edit it, surface the dashboard URL from url, previewUrl, or appUrls in the tool/CLI output. If needed, generate it with sequenzy urls or MCP get_app_urls.
  7. Destructive commands (delete, delete-variant, cancel-invitation, and similar) prompt for confirmation. Pass --yes (or -y) to skip the prompt; --yes is required when stdin is not a TTY, which covers most agent and CI runs.
  8. webhooks create returns a one-time signing secret. Surface it to the user immediately - it cannot be retrieved later.
  9. Call out implementation caveats that matter operationally, such as whoami using cached local auth state, sequence creation supporting both --goal and explicit step modes, explicit discount steps requiring Stripe before activation, generated sequences being capped at 10 emails, campaigns test being a stubbed success path in the current backend, and conditional email content requiring block JSON rather than raw HTML.

Dashboard URLs

Use SEQUENZY_APP_URL as the dashboard base when it is set; otherwise default to https://sequenzy.com.

Prefer actual URLs returned by the CLI/MCP result:

  • sequence editor: /dashboard/company/{companyId}/sequences/{sequenceId}
  • campaign editor: /dashboard/company/{companyId}/campaign/{campaignId}
  • campaign preview/review: /dashboard/company/{companyId}/campaign/{campaignId}?step=review
  • template/email editor: /dashboard/company/{companyId}/emails/{emailId}
  • settings: /dashboard/company/{companyId}/settings
  • settings tab: /dashboard/company/{companyId}/settings?tab={tab}

Useful settings tabs include domain, tracking, localization, integrations, events, tags, goals, sync-rules, api-keys, widgets, and team.

References

  • references/command-reference.md: exact command shapes, env vars, behavior, and caveats.
  • references/use-cases.md: decision trees and examples for the most common agent tasks.

Questions people ask

When should I use this skill instead of sequenzy-email-marketing?
Use Sequenzy when the user mentions Sequenzy broadly or asks a task that does not clearly map to email-marketing. For campaigns, subscribers, sequences, transactional email, and similar product work, sequenzy-email-marketing is narrower and should be preferred.
How does it avoid promising commands that are not actually wired up?
It treats `packages/cli/src/index.tsx` as the source of truth for wired CLI commands and `packages/mcp/src/tools/index.ts` for MCP tools, and refuses to claim support for anything that only appears in docs or `--help` text without an attached implementation.
What happens when the requested workflow is not implemented?
It states the gap plainly, points to the Sequenzy dashboard or direct API as the next-best path, and offers `sequenzy feedback "..." --category missing_capability` (MCP: `submit_feedback`) so the request reaches the Sequenzy team.

Related skills

Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.

by johnpatternai21 installs8 stars

Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.

by Iván555 installs18 stars

Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.

by fly0pants4.3k installs296 stars

Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.

by nssa.io1.0k installs47 stars

Post videos, photos, text, and documents to 10 social platforms through a single REST API call.

by victorcavero14375 installs50 stars

More from polnikale

Browse all skills

Operate Sequenzy email marketing through verified CLI and MCP workflows for subscribers, campaigns, sequences, and stats.

by polnikale19 installs

Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on responsi...

by polnikale3 installs

Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on Claude-o...

by polnikale3 installs

Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on fast del...

by polnikale3 installs

Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on workflow...

by polnikale3 installs

Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on behavior...

by polnikale1 installs