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/product-discovery.md
View on GitHub# Product discovery before outbound
Read the README and product docs, package manifests, main pages and routes, API routes, schema and models, integrations, authentication and onboarding, and the core workflow. Follow the files that reveal what value the product creates. Do not read secrets or change code during this pass.
Explain in plain English:
1. What the product appears to do and who uses it.
2. Valuable actions it can perform for one prospect.
3. Events that could change a follow-up, with file paths supporting each finding.
4. Which useful actions or events already exist and which would need to be built.
Then propose five distinct outbound workflows. Each should follow this chain:
signal → prospect → external context → action in this product → useful artifact → Sendsets email → interaction → product event → follow-up, branch, or stop
For each, give a name, why the prospect would care, the exact workflow, a short realistic first email, what Sendsets does, and what needs to be built. Prefer a finished result the prospect can inspect before a meeting. Ground capabilities in code; mark unbuilt steps as proposed. Avoid generic website summaries, name personalization, generic icebreakers, hiring signals, and enrichment presented as the deliverable.
End with a clear choice. Do not implement a workflow, alter code, provision mailboxes, or send anything until the user chooses an idea. If the repo is unavailable, ask for a product description and label all assumptions.
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: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |