mcpbeat

Outreach Manager

aaron-he-zhu/outreach-manager

Use 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. 达人邀约建联/合作谈判话术

7k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2500
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill outreach-manager

The instruction itself

10 sections, as written by the author

Outreach Manager

Craft personal, professional, persistent outreach; manage negotiations; track relationship progress. Home discipline is influencer (creator outreach), and the same mechanics engine — personalization, multi-touch cadence, negotiation scripts, pipeline tracking — serves media/analyst and launch-partner targets when press-media-relations hands over its media list, angles, and embargo terms, and social-selling / advocate-recruitment targets when social-selling-planner or advocacy-program-designer hands over a warm 1:1. The list, the angle, and the embargo stay with the handing-off skill; this skill owns the pitch execution.

Quick Start

Shortest invocation:

Write an outreach message to @[influencer] for [campaign]

Negotiate a gap between ask and budget:

Help me negotiate with @[influencer] who is asking for $[X] when our budget is $[Y]

Skill Contract

  • Reads: target influencer handle(s), platform, follower count, niche; campaign and product context; compensation type and budget; deliverables and timeline; any prior contact history supplied by the user or loaded from memory. Before any outreach, check memory/creators/<handle-slug>.md — the creator-registry roster record — for the confirmed contact path, last agreed rate, and negotiation/response history.
  • Writes: outreach artifact (pitches, follow-up sequence, negotiation guide, pipeline tracker) to memory/influencer/outreach-manager/YYYY-MM-DD-<topic>.md. When a cycle closes, the closed outcome (final agreed rate, response history, confirmed contact path) goes as a one-line update to memory/events/creators.ndjson via an authorized operation: propose request to registry-events.py — only creator-registry writes canonical roster records.
  • Promotes: durable facts (confirmed partners, agreed rates, top objection patterns, response-rate baselines) to memory/hot-cache.md.
  • Done when:
  • A personalized pitch (plus at least one variation) exists for each target influencer.
  • A follow-up cadence and pipeline status are recorded for every contacted creator.
  • Confirmed partners are flagged with agreed terms for handoff.
  • Primary next skill: creator-content-auditor

Handoff Summary

> Emit the standard shape from skill-contract.md §Handoff Summary Format.

Data Sources

This family needs no live integrations (Tier 1). The skill works entirely from inputs you provide — paste the influencer handles, follower counts, niche, budget, and deliverables, and it produces every artifact without any tool connection.

Where a connector could speed up the work, use these ~~ placeholders:

  • ~~influencer database — pull handle, follower count, niche, and past partnerships instead of typing them.
  • ~~social platform analytics — verify audience demographics and recent posts for personalization.
  • ~~CRM — sync pipeline status, last-contact dates, and next actions.
  • ~~email/DM tool — schedule and send the follow-up cadence.

See CONNECTORS.md for the free/keyless recipe per category. No integration is required; when one is absent, ask the user for the inputs directly. Missing target or campaign details do not block a reversible draft: use explicit bracketed placeholders, generalize any unverified personalization, and identify the smallest inputs needed to finish it.

Instructions

When a user requests outreach help, run these steps. Each step has a fill-in template in references/templates.md — copy the matching block and replace the placeholders. Apply the hard copy rules in references/cold-copy-rules.md before any message ships.

Draft/send boundary: drafting is reversible; sending or scheduling is an external side effect. Even when the shortlist or personalization facts are missing, produce an inline first-touch draft labeled DRAFT — NOT SENT with explicit placeholders and no invented facts, then state what is still needed for personalization. Never stop with only an input request when a safe placeholder draft can be produced. Do not send or schedule anything until the user explicitly approves the exact recipients, channel, and message or cadence.

  • Gather outreach context — capture campaign/product context, target handle(s), platform, followers, niche, compensation type, budget, deliverables, and timeline. Load the memory/creators/<handle-slug>.md roster record first when it exists — re-engaging a rostered creator starts from the confirmed contact path and last agreed rate, not a cold pitch. Template: Step 1.
  • Create personalized outreach — list personalization points (recent content, style, audience, values, past partners), then write the primary message plus a DM-friendly short version and a formal email/management version. Template: Step 2. *Media/analyst/hunter targets*: personalize on beat and recent coverage, lead with the story angle (not a compensation offer), carry the embargo terms verbatim from the press-media-relations artifact, and never invent quotes or data — claims come from the approved message house.
  • Create follow-up sequence — build a 4-touch cadence (Day 0 / 3-4 / 7-8 / 14, then archive at Day 21), each touch adding new value and getting shorter. Cap at 3-4 follow-ups; make it easy to say no. Template: Step 3.
  • Provide negotiation support — map the ask/budget gap, then apply value-exchange, scope-adjustment, or future-value strategies with ready scripts and an objection/response table. Template: Step 4.
  • Track outreach pipeline — record stage counts and conversion rates, a per-creator detailed pipeline, today's prioritized actions, and pipeline health (response rate, confirmation rate, time-to-confirm, top objection). Template: Step 5. Active-cycle tracking lives here; when a cycle closes (confirmed or archived), submit the closed outcome as a one-line update to memory/events/creators.ndjson via an authorized operation: propose request to registry-events.py for creator-registry to reconcile.

Example

User: "Write outreach for @sustainablesarah (45K Instagram followers, eco-lifestyle) for our organic skincare launch"

Output (abridged):

## Outreach for @sustainablesarah

### Personalization Points
- Recent post: "5 swaps for a zero-waste bathroom"  •  Style: educational, authentic  •  Past partners: Grove Collaborative

### Primary Message
Subject: Love your zero-waste content – collab with [Brand]?

Hi Sarah! I just watched your "zero-waste bathroom" post and added reusable cotton rounds to my cart 😊 I'm [Name] from [Brand] — organic skincare in fully compostable packaging. We're launching a new collection and thought of you. We'd love to send the full line, and if you love it, partner on a post + Stories. Offering $[X] plus product and full creative freedom. Interested?

Full multi-version output, follow-up cadence, negotiation guide, and pipeline tracker live in references/templates.md.

Reference Materials

  • references/templates.md — fill-in templates for all five steps, the full worked example, and outreach tips.
  • references/cold-copy-rules.md — hard cold-outreach copy rules: first-line bans, per-step sentence caps, soft CTAs, observation framing, no link in step 1.
  • skill-contract.md — shared contract and Handoff Summary format.
  • state-model.md — memory tiers and save-path conventions.
  • CONNECTORS.md — free/keyless data recipe per connector category.
  • STAR benchmark scoring at references/star-benchmark.md — quality scoring reference for downstream review.
  • expert-panel.md — multi-persona review method for pressure-testing outreach copy before sending.
  • Sibling skills: influencer-discovery, fit-scorer, brief-generator, contract-helper, creator-content-auditor.

Next Best Skill

  • Primary: creator-content-auditor — once a partner is confirmed and creates content, review the draft against the brief before it ships.
  • Alternate: contract-helper — finalize agreed terms into a partnership agreement.
  • Alternate: brief-generator — send a full campaign brief to a creator who asked for more detail.

Termination note: keep a visited-set. If a skill in this chain was already invoked this session, stop and report chain-complete rather than re-running it. Max handoff depth is 3.

  • influencer-discovery - Find influencers to reach out to
  • fit-scorer - Prioritize who to contact first
  • brief-generator - Send briefs to confirmed partners
  • contract-helper - Finalize agreements

How to use it

Copy the folder

Take aaron-he-zhu/outreach-manager from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.