# Sendsets for coding agents

You are helping a customer use Sendsets to turn their own product into a useful outbound workflow. Read the [Sendsets skill](https://sendsetsapi.com/skills/sendsets/SKILL.md) first. Its references live beside it under `/skills/sendsets/references/`; read only the ones needed for the current step. Save the published skill folder in your global skills directory for future sessions (`~/.claude/skills/sendsets/` for Claude Code or `~/.codex/skills/sendsets/` for Codex), preserving its relative paths. Keep the customer's repository unchanged during product discovery. The CLI is `sendsets`.

## First outcome: understand the product

Before connecting a mailbox or configuring a campaign, inspect the current codebase. Read its README and docs, package manifests, main pages and routes, API handlers, schema and models, integrations, auth and onboarding, and core product workflow. Do not read secrets or modify code during this pass.

Tell the user what the product appears to do, who it serves, which valuable actions it can perform for one prospect, and which product events could change outreach. Cite files for existing capabilities and label missing pieces.

Propose five distinct campaigns where the product creates a useful artifact before the first email. For each give a name, why it works, the exact chain of tools and actions, a short first email, Sendsets' role, and what needs to be built. Use this chain:

signal → prospect → external context → action inside this product → useful artifact → Sendsets email → interaction → product event → follow-up, branch, or stop

Avoid generic company-name personalization, website summaries, hiring signals, and AI icebreakers. The user should be able to say “2” and know what the campaign would actually deliver. Stop and wait for that choice before making code changes.

If there is no codebase, ask for the product's URL or a description and clearly mark assumptions.

## After the user chooses an idea

Install the CLI if needed. On macOS and Linux, use the verified [CLI installer](https://sendsetsapi.com/cli.sh) and its [checksum](https://sendsetsapi.com/cli.sh.sha256), or follow `scripts/install.sh` in the skill. On Windows, use `https://sendsetsapi.com/cli.ps1`. Confirm with `sendsets version`.

Run `sendsets auth status --json`. If sign-in is needed, `sendsets login` prints a code and approval URL. Show them to the user; browser approval is theirs. Then run `sendsets whoami --json` and `sendsets doctor --json`. A fresh workspace may need a mailbox or app connection. Explain what is missing and configure only what the chosen workflow needs.

Use the relevant skill references for campaigns, mailboxes, warmup, replies, and integrations. Inspect the actual product endpoint and event code before wiring an app action or follow-up branch. Build the chosen workflow, validate it, run preflight, and show the exact first email.

A test email or single-prospect test sends real mail. Ask before that specific send. Provisioning a managed mailbox creates a recurring charge, so show a live quote before ordering. Do not launch a full campaign unless the user explicitly asks to send; test approval is separate from launch approval.

The first useful message should sound like: “I read your product. Here are five ways I think it could sell itself. Pick one and I’ll build the campaign.”