# Manage Sequenzy Workflows With CLI Guidance

Sequenzy tasks can span many CLI and MCP commands. This skill maps requests to supported workflows, caveats, and review links.

## Install

```bash
npx skillstore add sequenzy/sequenzy
```

## Metadata

- Status: approved
- Slug: sequenzy-sequenzy
- Skillstore revision: r1
- Version status: missing
- Tree hash: e34258a59f943e6360be48754e1c56243966975b1fba1670f4d8448d5ee59b39
- Author: Sequenzy
- GitHub username: Sequenzy
- License: MIT
- Repository: https://github.com/Sequenzy/skills/tree/main/skills/sequenzy
- Ref: 62e2a730c5cd74eab4c7164309d810de660fcea3
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, env\_access, external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sequenzy-sequenzy
- Manifest: https://skillstore.pages.dev/api/skills/sequenzy-sequenzy/manifest

## Capabilities

- Maps broad Sequenzy requests to supported CLI and MCP workflows.
- Documents auth, account, company, subscriber, list, tag, segment, template, campaign, and sequence tasks.
- Explains campaign scheduling, lifecycle control, duplicate modes, and dashboard URL generation.
- Covers webhook management, delivery replay, signing secret handling, and product file attachment.
- Calls out unsupported immediate campaign sends and backend caveats.

## Use Cases

- Plan a Campaign Launch: Map draft creation, scheduling, test requests, labels, reply profiles, and review links before launch.
- Maintain Subscriber Data: Choose safe commands for lists, tags, segments, imports, removals, and sequence enrollment checks.
- Configure Developer Integrations: Manage webhooks, websites, products, delivery files, API keys, and dashboard URLs with documented caveats.

## Prompt Templates

### Check Authentication

```
Check whether this machine is authenticated with Sequenzy. If not, tell me the safest next step without exposing any secret.
```

### Prepare a Campaign

```
Prepare a Sequenzy campaign workflow for [campaign name]. Include required inputs, supported actions, review links, and safety checks.
```

### Maintain a Subscriber List

```
Help me update [list name] with [subscriber source]. Validate the input, explain limits, and ask before changing live data.
```

### Audit a Complex Workflow

```
Review this Sequenzy workflow request: [details]. Map each step to supported CLI or MCP actions, identify unsupported parts, and list approval gates.
```

## Limitations

- It is a guide, not the Sequenzy CLI or API.
- It relies on authenticated Sequenzy access outside the skill files.
- Some workflows require the dashboard or direct API use.
- Many examples can change live workspace data if executed.

## Best Practices

- Inspect existing resources before making mutations.
- Ask for explicit approval before destructive or permission-changing commands.
- Use dashboard URLs returned by CLI or MCP results for final review.

## Anti Patterns

- Passing --yes to destructive commands without explicit user approval.
- Assuming unsupported workflows exist because related nouns appear in docs.
- Posting API keys or signing secrets into shared logs.

## Security Audit

- Audited at: 2026-07-05T21:05:33.757\+00:00
- Summary: Static findings are largely documentation false positives: Markdown command names, example URLs, and environment variable names rather than executable code. Semantic review found real operational risk because the skill guides authenticated Sequenzy mutations, destructive confirmation bypass, and one-time secret handling.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 0
- Popularity score: 0