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/integrations.md

View on GitHub
# Product actions and events

A campaign can call the user's product for one prospect through an app connection. Inspect the actual endpoint and payload before proposing an `app_action`. Use `sendsets connection create --help` and `sendsets connection test CONNECTION_ID --json` to configure and verify it.

The product can report behavior with `sendsets events send EVENT_NAME --email PROSPECT_EMAIL --data JSON`, or through the API. Map only events the app can emit or clearly list the missing instrumentation. A `wait_for_event` step can branch or stop follow-up after a view, signup, activation, feature use, or upgrade. Make the event identity and timing explicit so a prospect cannot affect another prospect's campaign.

Clay, Firecrawl, HubSpot, and other tools are optional sources of prospects or context. Check available integrations and permissions before claiming an automated connection exists. The differentiating step is the useful action inside the customer's product, not a generic enrichment field.
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