What does this skill do, and when should you use it?
Outreach Manager is the activate-phase skill for the influencer discipline in Aaron Marketing Skills. It turns supplied target, campaign, budget, deliverable, and contact-history data into personalized pitches, follow-up sequences, negotiation scripts, and pipeline records. The same outreach mechanics can serve journalists, analysts, hunters, launch partners, social-selling contacts, and advocates when upstream skills provide the relevant list or warm introduction. It is a good fit for teams that need repeatable creator outreach without requiring live integrations.
Reads influencer handles, platforms, follower counts, niches, campaign and product context, compensation type, budget, deliverables, timeline, and prior contact history; checks memory/creators/<handle-slug>.md when available for the confirmed contact path, previous rate, and negotiation history; identifies personalization points and writes primary, short DM, and formal email or management versions; creates a four-touch cadence for Day 0, Days 3-4, Days 7-8, and Day 14, followed by archiving at Day 21; maps ask-versus-budget gaps and supplies value-exchange, scope-adjustment, future-value, and objection-response scripts; records stage counts, conversion rates, creator-level status, next actions, and pipeline health; writes outreach artifacts under memory/influencer/outreach-manager/ and proposes closed outcomes for creators.ndjson through the authorized registry process.
- A brand team is launching a product and needs a personalized Instagram creator pitch based on recent content and audience fit.
- A marketer needs scripts for responding when a creator's rate exceeds the available campaign budget.
- An outreach lead wants a four-touch sequence for non-responders with a clear archive point.
- A launch team has received a media list and story angle from press-media-relations and needs to execute the pitch.
- A social-selling or advocacy team has a warm one-to-one contact and needs to move the relationship through a tracked pipeline.
How do you install this skill?
- Verify every personalization claim, rate, contact path, link, disclosure, and platform-compliance detail before sending; the skill does not define a clear user-confirmation gate for dispatch.
- The cold-outreach rules conflict with the templates and example, especially the ban on opening with “I”; manually reconcile the copy before use.
- Memory may contain contact and commercial-term data, but the skill provides no specific redaction, retention, or recovery procedure.
- The pipeline template’s industry-average response and confirmation rates are unsourced placeholders and should not be treated as verified benchmarks.
- Local filesystem
Install the collection in Claude Code with /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, followed by /plugin install aaron-marketing@aaron. For a compatible Agent Skills host, use npx skills add aaron-he-zhu/aaron-marketing-skills; the README also documents the -s option for a single skill, such as npx skills add aaron-he-zhu/aaron-marketing-skills -s outreach-manager. The repository is licensed under Apache-2.0.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/influencer/activate/outreach-manager" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Provide a target and campaign context, for example: Write an outreach message to @sustainablesarah for our organic skincare launch. For negotiation, use: Help me negotiate with @influencer who is asking for $X when our budget is $Y. Include the platform, follower count, niche, budget, deliverables, timeline, and any previous contact history. The skill does not require a live connector; provide the source inputs directly when external data is unavailable.
What are this skill's strengths and limitations?
- Covers the full execution loop from first pitch through follow-up, re-engagement, negotiation, and pipeline tracking.
- Produces multiple communication formats, including a primary pitch, short DM, and formal email or management version.
- Records confirmed partners and agreed terms for downstream handoff.
- Works from user-supplied data without requiring live integrations or paid tools.
- Defines clear boundaries with creator-registry, contract-helper, brief-generator, press-media-relations, and creator-content-auditor.
- Does not discover or rank creators, and does not independently verify audience data; those inputs must be supplied or retrieved through an optional connector.
- Does not finalize signed agreements, tier media lists, embargo terms, or press-release structure.
- The source does not show that the skill itself sends messages, schedules follow-ups, or synchronizes a CRM.
- The source material provides no independent test-suite or platform-coverage evidence for this individual skill.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Outreach Manager this page | 46 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Market Launch Playbook Generator | 52 · Use with care | ★ 2.8k | 7mo ago | MIT |
| Influencer Discovery | 51 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Content Amplifier | 50 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Offer & Claims Registry | 60 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
Unlike influencer-discovery and fit-scorer, this skill does not source or prioritize creators; it executes outreach and negotiation. Unlike contract-helper, it works toward agreed terms but does not finalize the partnership agreement. Unlike press-media-relations, it executes a media pitch after receiving the list, angle, and embargo terms. Unlike creator-content-auditor, it operates before submitted creator content is reviewed for publication.
How did FollowSkills review this skill?
The skill declares no live integrations, keeps connectors optional, and routes canonical registry changes through an operation: propose request, showing some permission boundaries. However, it reads and writes contact paths, rates, and contact history in memory without explicit minimization, redaction, user confirmation, send-before approval, or rollback guidance, so points are deducted.
Inputs, outputs, workflow steps, and the fallback of asking the user for missing inputs are reasonably clear. Static evidence also shows an internal conflict: the cold-copy rules prohibit opening with “I,” while templates include “I’ve been following...” and “I hope...”; there are no skill-specific tests or diagnosable abnormal-input messages, so the score remains conservative under the static cap.
Triggers, target types, inputs, outputs, and boundaries with contract-helper and press-media-relations are fairly explicit, and the skill documents a no-connector path using user-provided data. However, the content and templates are predominantly English, evidence for Chinese-user adaptation is limited, and degradation rules for missing platform data, history, or verified content are underdeveloped, so points are deducted.
The skill provides structured front matter, versioning, an Apache-2.0 license declaration, Quick Start, contract, templates, copy rules, limitations, and next-skill guidance, with good information architecture. Maintenance ownership, update path, and changelog practice are not clearly established in the supplied skill evidence; additionally, SECURITY.md lists 17.x as the supported line while the skill declares 18.0.0, so full marks are not justified.
It covers personalized pitches, multi-touch follow-up, negotiation scripts, and pipeline tracking, and its templates can produce a basic usable artifact. However, the output depends on many placeholders and user-supplied facts, conflicting template rules can require substantial revision, and no key-path execution evidence is supplied; under static calibration the score cannot exceed 7 and is reduced further.
The materials include documented rules, templates, contract references, and repository-level tests and CI evidence. The supplied tests primarily cover architecture and audit artifacts rather than this outreach skill’s key paths, and there is no third-party execution evidence or independent reproduction, so only limited credit is warranted.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →