Sequenzy

Overview

Use this skill when the task is to operate Sequenzy, not to change Sequenzy's source code. Prefer the sequenzy CLI for supported workflows and explicitly call out when a requested workflow is not wired in the current implementation.

Ground Rules

1. 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 behavior, payload shape, and API routes.
3. Do not promise support for commands that only appear in docs or --help text without an attached action handler.
4. Prefer sequenzy login for interactive auth and SEQUENZY_API_KEY for automation.
5. 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 INLINECODE7
• account inspection with INLINECODE8
• company inspection or creation with INLINECODE9
• stats overview or stats by campaign/sequence ID
• subscribers list, add, get, and INLINECODE13
• lists list and INLINECODE15
• tags INLINECODE16
• segments list, create, and INLINECODE19
• templates list, get, create, update, and INLINECODE24
• campaigns list, get, create, update including reply-to updates, and INLINECODE29
• sequences list, get, create, update, enable, disable, and INLINECODE36
• websites list, add, check, and INLINECODE40
• API key creation with INLINECODE41
• send one transactional email by template or raw HTML

Unsupported Or Placeholder Workflows

Treat sequenzy generate ... as unsupported placeholder surface. Also treat missing subcommands as unsupported even when the noun exists. For example: campaign send/schedule flows, list deletion, tag mutation, and bulk subscriber import are not available through the current CLI handlers.

Execution Pattern

1. 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 HTML 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.
6. Call out implementation caveats that matter operationally, such as whoami using cached local auth state, sequence creation supporting both --goal and explicit step modes, and campaigns test being a stubbed success path in the current backend.

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.