Skip to content

hashgraph-online/awesome-codex-plugins / plugins/AddisonHoff/sendsets/skills/sendsets

sendsets

Verified

Use 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.

FileKindSize
SKILL.mdskill md2.5 KB
assets/campaign.example.yamlconfig672 B
references/authentication.mdmarkdown885 B
references/campaigns.mdmarkdown3.6 KB
references/install.mdmarkdown1.0 KB
references/integrations.mdmarkdown1017 B
references/mailboxes.mdmarkdown1.1 KB
references/product-discovery.mdmarkdown1.5 KB
references/replies.mdmarkdown814 B
references/warmup.mdmarkdown659 B
scripts/doctor.shexecutablescript238 B

references/install.md

View on GitHub
# CLI installation

Install the CLI with `brew install addisonhoff/tap/sendsets` (macOS, Linux) or `scoop bucket add sendsets https://github.com/AddisonHoff/homebrew-tap` then `scoop install sendsets` (Windows). Without a package manager, download the archive for your platform and `checksums.txt` from https://github.com/AddisonHoff/sendsets-releases/releases/latest, check the archive against `checksums.txt`, and unpack the `sendsets` binary onto PATH.

Confirm with `sendsets version`. The Unix binary defaults to `~/.local/bin/sendsets`; use that path if the current shell has not loaded the new PATH. A hosted workspace uses the default host. For self-hosted use `SENDSETS_HOST` or `--host`.

Run `scripts/doctor.sh` after authentication. It checks auth and calls `sendsets doctor --json`. A fresh workspace can report missing mailboxes or app connections. These are next actions, not evidence that the CLI install failed.

`assets/campaign.example.yaml` is an editable example for `sendsets run`. Check the current CLI help before adapting it to a customer campaign.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall