JasonColapietro/suede-creator-skills / skills/suede-influencer-outreach
suede-influencer-outreach
VerifiedUse when asked "pitch this creator" or to repair an influencer or B2B creator-program first touch. Suede grounds one message in a named audience fact, states real compensation and one ask, fits the published contact route and stops the two-follow-up plan at a positive reply. NOT FOR: affiliate mechanics (use suede-referrals), brand partnerships (use suede-co-marketing), cold B2B email (use suede-cold-email), or journalist pitches (use suede-public-relations).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.8 KB |
| SKILL.md | skill md | 11.0 KB |
| agents/openai.yaml | config | 571 B |
| evals/evals.json | config | 3.8 KB |
| references/channel-and-manager.md | markdown | 2.7 KB |
| references/examples.md | markdown | 4.4 KB |
| references/follow-up-cadence.md | markdown | 2.3 KB |
| references/pitch-anatomy.md | markdown | 6.5 KB |
| references/usage-contract.md | markdown | 896 B |
references/follow-up-cadence.md
View on GitHub# Follow-Up Cadence
Cadence is the best-sourced part of creator outreach. Independent practitioner accounts converge on the same shape: a small number of spaced follow-ups, then stop.
## Three Cadences, Ranked
Default order, best value per unit of effort first. A hard deadline or a long-term relationship goal moves it.
1. **Two follow-ups, hard stop at three messages.** First follow-up about a week after the pitch, second about two weeks after that. Captures the realistic yield from a busy creator without tipping into aggravation. Practitioners running creator programs report planning for exactly this and stopping at three.
2. **One follow-up at five to seven business days, then move on.** Near-zero extra effort and most replies land in that window. Misses the creator who was simply traveling. Best when a launch date is close.
3. **Long tail for a must-have creator.** After the standard pair, one light touch at about a month, then three months, then six. Each touch needs a genuinely new reason. Only works when someone owns the file across quarters.
By value alone: long tail, then two follow-ups, then one. By effort: the same order.
**Promote the long tail** when the user names a creator as a priority and someone will own the log. **Delete it** when nobody will. An unowned reminder fires six months later with nothing new to say.
## Follow-Up Copy Rules
- One or two sentences. Nothing from the first touch restated.
- Each one carries a new small angle: a proof point held back from message one, an easier version of the ask, or a real timing hook.
- Never "just checking in", "bumping this", or "did you see my email?".
- Low pressure by design. Silence means busy, not rejection. A guilt-trip turns a busy creator into a lost one.
- Same channel as the first touch. Switch only if the first channel was a guess and a better-listed contact has surfaced since.
## Stop Rules
- **Positive reply at any point:** stop the sequence and hand off to negotiation with the compensation facts unchanged.
- **Silence after the final message:** close the file. Reopen only with something new, such as a relevant launch or a changed offer. Never re-send.
- **A no is a no.** Log it with the reason if given, and do not re-pitch the same offer.
## B2B and B2C
This guidance is published without a business-model split. Apply the same plan to both.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |