aiskillstore/marketplace / skills/aaron-he-zhu/outreach-manager
outreach-manager
VerifiedUse when the user asks to "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", or "negotiate partnership terms"; produces personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker — the shared outreach mechanics engine for creator, media/analyst, launch-partner, and social-selling / advocate-recruitment targets. Not for finalizing signed agreements — use contract-helper; not for media-list tiering, embargo terms, or press-release structure — use press-media-relations. 达人邀约建联/合作谈判话术
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.9 KB |
| references/cold-copy-rules.md | markdown | 3.4 KB |
| references/templates.md | markdown | 11.8 KB |
| skill-report.json | config | 41.2 KB |
references/cold-copy-rules.md
View on GitHub# Cold Outreach Copy Rules
Hard rules for cold creator outreach (first-touch DM or email to someone who has never heard from you). Apply to every message in every follow-up sequence. These are stricter than the warm-pitch templates in `SKILL.md` — use them when the relationship is cold and deliverability matters.
---
## First-Line Bans
Never open the first message with any of these — they read as a template and get skipped:
- "I" — e.g., "I came across your profile..."
- "We" — e.g., "We help creators like you..."
- "Our team" / "Our brand" as the first words
- "I wanted to" / "I'm reaching out because..."
- "Hope this finds you well" or any version of it
- "My name is..." — save for a later step if needed, never step 1
Always open with one of these instead:
- The creator's name plus a specific thing they made — "Sarah, your zero-waste bathroom post..."
- A specific observation about their content — "Your last three reels all lean educational, not salesy..."
- A relevant trend in their niche — "Since refillable packaging took off this year..."
The first line earns the second. If it does not make the creator think "this is about me," the message is dead.
---
## Per-Step Sentence Caps
| Step | Max sentences | What it does |
|------|--------------|--------------|
| Step 1 (first touch) | 3 sentences | Personal opener, the offer, one soft CTA. Nothing else. |
| Steps 2-3 (follow-up) | 3-5 sentences | Add a new angle or a new piece of value, never a repeat. |
| Bump (short nudge) | 1-2 sentences | "Still a fit?" style. Short. |
| Breakup (final) | 2-3 sentences | Leave value, keep the door open. |
If a step runs longer than its cap, cut it.
---
## Observation, Not Study
Frame social proof as earned experience, not a marketing claim.
- Good (observation): "Most skincare creators we work with see saves spike when the routine is filmed in one take."
- Bad (study-like): "According to our data, 73% of creators perform better with..."
Observation sounds like a peer who has done this before. A statistic sounds like a pitch deck. Creators believe the first.
Never fabricate: client names, follower or sales numbers, past-campaign results, or content references unless they are real and verifiable. If you cannot verify it, generalize it.
---
## Soft CTA List
Use a low-commitment ask in step 1. Preferred soft CTAs:
- "Worth a look?"
- "Want the full brief?"
- "Open to hearing more?"
- "Is this the kind of thing you take on?"
- "Happy to send details — useful?"
Avoid hard asks in step 1 — they presume interest from a stranger:
- "Book a call with me"
- "Are you free Thursday?"
- "Let's hop on a call"
Use a hard ask only at step 3+ after the creator has replied or signaled interest, and even then soften it.
---
## No Link in Step 1
- Step 1: no links at all. Links in a first cold message hurt deliverability and read as spray-and-pray.
- Steps 2-3: at most one link, only if it adds real value (a brief, a lookbook, a past-collab example).
- Breakup: one real, genuinely useful link is fine.
- Never link to a form or landing page in steps 1-2.
- Never invent a URL. Every link must point to a real, checked page before sending.
---
## Tone
Peer-to-peer, not brand-to-creator. Curious, not desperate. Specific, not generic. Short, not comprehensive. If a message sounds like marketing copy, rewrite it until it reads like a note from a knowledgeable peer.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |