Sequenzy

Agent guide for operating Sequenzy. Use when Codex needs to authenticate, inspect identity, manage subscribers, create or edit campaigns/sequences/templates,...

Security Scan

The skill's instructions, scope, and resource needs are coherent with its stated purpose of operating Sequenzy (CLI/dashboard/API) and do not request unrelated credentials or installs.

Purpose & Capability

Name and description match the SKILL.md: the document describes using the Sequenzy CLI, dashboard, and API to manage subscribers, templates, campaigns, sequences, stats, and sends. The requested capabilities (auth via SEQUENZY_API_KEY or interactive login) are appropriate for those tasks.

Instruction Scope

Instructions are narrowly scoped to Sequenzy workflows (run sequenzy CLI commands, check SEQUENZY_API_KEY, generate dashboard URLs, validate IDs). They reference repository paths (packages/cli, packages/mcp) as sources of truth — useful guidance but only actionable if the agent has that repo available. No instructions to read unrelated files or exfiltrate data.

Install Mechanism

Instruction-only skill with no install spec and no code files to write or run locally; lowest-risk install profile.

Credentials

The skill does not require any unrelated environment variables. It documents optional variables (SEQUENZY_API_KEY, SEQUENZY_API_URL, SEQUENZY_APP_URL) that are directly relevant to operating Sequenzy. The registry metadata lists no required secrets, which is consistent with the skill being able to operate interactively or using an optional API key.

Persistence & Privilege

always:false and no install actions; the skill does not request permanent platform presence or elevated privileges. Autonomous invocation is allowed (platform default) but not combined with any broad or unrelated environment access.

Assessment

This skill is a usage guide for operating Sequenzy via its CLI, dashboard, or API and appears internally consistent. Before enabling, consider: (1) If you provide SEQUENZY_API_KEY, the agent could perform management actions (create/update templates, send transactional emails) — restrict the key's scope and use a dedicated automation key if possible. (2) The skill favors running the `sequenzy` CLI and reading local Sequenzy config (e.g., cached auth); ensure the agent environment has the expected CLI and does not expose unrelated secrets. (3) The SKILL.md references repository source files as the 'source of truth' — that is only helpful if the agent can access that repo. (4) For safety, require explicit confirmation before any destructive actions (hard deletes, hard unsubscribes, sending emails), and test changes in a sandbox company or with a limited API key. If you need deeper assurance, ask the skill author for a provenance/homepage or a signed release and review how your environment supplies SEQUENZY_API_KEY to the agent.

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, 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 or creation with companies list|get|create
• stats overview or stats by campaign/sequence ID
• subscribers list, add, get, and remove
• lists list and create
• tags list
• segments list, create, and count, including --match any in the CLI and filterJoinOperator: "or" in MCP/API calls
• templates list, get, create, update, and delete, with create and update accepting raw HTML or Sequenzy block JSON
• campaigns list, get, create, update including reply-to updates, and test, with create accepting raw HTML, Sequenzy block JSON, or prompt-generated content and update accepting raw HTML or Sequenzy block JSON
• MCP update_campaign calls including replyTo and replyProfileId
• sequences list, get, create, update, enable, disable, and delete
• AI generation with generate email, generate sequence, and generate subjects
• 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
• API key creation with api-keys create
• send one transactional email by template or raw HTML

Unsupported Or Placeholder Workflows

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. 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.
6. When you create or inspect a campaign, sequence, template, or company and the user may want to review/edit it, surface the dashboard URL from url or appUrls in the tool/CLI output. If needed, generate it with sequenzy urls or MCP get_app_urls.
7. Call out implementation caveats that matter operationally, such as whoami using cached local auth state, sequence creation supporting both --goal and explicit step modes, 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}
• 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.