跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

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

aaron-he-zhu · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add aaron-he-zhu/aaron-marketing-skills --skill outreach-manager

技能说明


name: outreach-manager slug: outreach-manager displayName: "Outreach Manager · 建联外联管理" summary: "红人及媒体建联:分层触达序列、跟进节奏与回复率优化" description: '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. 达人邀约建联/合作谈判话术' version: "20.2.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_to_use: "Activate the skill when the user wants to contact a creator, journalist, analyst, hunter, or launch partner; draft or personalize a pitch message; build a follow-up cadence for non-responders; re-engage a past partner; negotiate rate or scope; handle pricing objections; or track outreach status across a target list. For media targets the list/angle/embargo artifact comes from press-media-relations — this skill executes the pitch mechanics." argument-hint: " [platform] [budget]" metadata: {"author": "aaron-he-zhu", "version": "20.2.0", "discipline": "influencer", "phase": "activate", "geo-relevance": "low", "hermes": {"tags": ["marketing", "influencer", "activate"], "category": "influencer"}, "openclaw": {"emoji": "📣", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}

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: a stable opaque creator_ref when one is carried by an authorized upstream artifact, plus transient target handle/profile locator(s), platform, follower count, niche; campaign and product context; compensation type and budget; deliverables and timeline; jurisdiction, intended channel, lawful-basis reference, contact-source/eligibility evidence, and pseudonymous consent subject ID; any prior contact history supplied by the user or loaded from memory. For a rostered creator, reuse a creator-registry aggregate ID only when its identity link is verified, resolve it through the authorized artifact or verified registry link, then check memory/creators/<aggregate-id>.md — the creator-registry projection — for the confirmed contact path, last agreed rate, and negotiation/response history. Never derive the path from a raw handle.
  • Writes: return the outreach artifact inline by default; save it to memory/influencer/outreach-manager/YYYY-MM-DD-<topic>.md only with exact WARM-save authorization. Reuse an explicitly carried opaque creator_ref, or a verified creator-registry aggregate ID; otherwise generate one random creator-<UUIDv4> once for this lineage. Never derive creator_ref from a raw handle, name, profile URL, email, provider ID, or deterministic hash. Before saving, replace raw locators and resolved recipient identities with the stable creator_ref and resolvable opaque recipient_ref, contact_source_ref, handle_ref, and evidence/approval references. A raw URL or handle is never a persisted source_ref. When no authorized source artifact or verified registry link can resolve an opaque identity/contact ref, set identity_status: unresolved, save no hidden raw-locator mapping, set cross_session_locator_required: true, and request the transient locator again at dispatch. Never persist a raw handle, name, profile URL, email, phone, postal address, provider ID, or credential. When a cycle closes, each outcome update (final agreed rate, response history, confirmed contact-path reference) requires a separate exact authorization for an operation: propose request to memory/events/creators.ndjson; only creator-registry writes canonical roster records.
  • Promotes: only with separate exact authorization, promote 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.
    • Every personalization fact records source_ref and observed_at; unverifiable facts remain placeholders or are omitted.
    • A follow-up cadence and pipeline status are recorded for every contacted creator, including terminal no-contact states.
    • Jurisdiction, channel, lawful basis, and contact eligibility are explicit; any send/schedule remains gated by exact approval and a live suppression check.
    • Confirmed partners are flagged with agreed terms for handoff.
  • Primary next skill: contract-helper

Handoff Summary

Emit the standa

阅读完整来源 ↗