hashgraph-online/awesome-codex-plugins / plugins/AddisonHoff/sendsets/skills/sendsets
sendsets
VerifiedUse Sendsets to turn a software product into useful outbound campaigns, then operate mailboxes, warmup, campaigns, replies, and product integrations through the CLI. Use when the user asks to set up or run cold email with Sendsets or wants campaign ideas grounded in their codebase.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| assets/campaign.example.yaml | config | 672 B |
| references/authentication.md | markdown | 885 B |
| references/campaigns.md | markdown | 3.6 KB |
| references/install.md | markdown | 1.0 KB |
| references/integrations.md | markdown | 1017 B |
| references/mailboxes.md | markdown | 1.1 KB |
| references/product-discovery.md | markdown | 1.5 KB |
| references/replies.md | markdown | 814 B |
| references/warmup.md | markdown | 659 B |
| scripts/doctor.shexecutable | script | 238 B |
references/authentication.md
View on GitHub# Authentication
Run `sendsets auth status --json` first. If already signed in, continue. Otherwise `sendsets login --hostname sendsetsapi.com` prints a code and approval URL; pass them to the user, since browser approval is theirs. Confirm with `sendsets auth status --json` and `sendsets whoami --json`.
A supplied key can be piped to `sendsets login --hostname sendsetsapi.com --with-token`. For automation, `SENDSETS_TOKEN` overrides stored credentials without saving the token; set `SENDSETS_HOST=sendsetsapi.com` with it, because CLI v0.4.24 and older default to a retired host. Never echo a token to logs or infer one from the codebase. Exit code 4 indicates missing, invalid, or insufficient credentials; use the CLI's fix message.
The user may need to select a workspace after sign in. Read the effective scopes and agent policy from `whoami` before a sensitive operation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |