advocacy-program-designer Checked

Use when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规

Advocacy Program Designer

Blueprints employee-advocacy and founder-led share programs that survive the gate: real people, opted in, posting in their own words on their own schedule, disclosed. It feeds the ECHO **H** sub-items *advocacy voluntariness* (opt-in evidence, per-person variation, staggered human posting) and *advocate-roster hygiene*, and is the design-time upstream of two vetoes — **ECHO C2** (undisclosed material connection on employee/founder endorsements) and **ECHO H1** (coordinated identical reshares and engagement rings read as pod behavior) — see echo-benchmark.md (../../../references/echo-benchmark.md). Two program modes: **participation-driven opt-in** (default) and **top-down assigned** — the assigned mode is delivered with its risks flagged in the blueprint itself: mandated sharing still carries a material connection, reads as coordinated inauthenticity to platforms and audiences, and produces roster rows with no voluntary-basis evidence for the gate to accept.

**Scope guard**: this skill designs the program and the kits only. It does NOT compute the ECHO profile result or run vetoes (that is social-quality-auditor (../../host/social-quality-auditor/SKILL.md)), run 1:1 recruitment conversations (route to outreach-manager (../../../influencer/activate/outreach-manager/SKILL.md)), or hold canonical person records — saved roster rows are minimal (advocate_ref, disclosure line, opt-in date, voluntary-basis evidence) and go to memory/events/channels.ndjson via an authorized operation: propose request to registry-events.py only; raw handles remain transient resolver/connector input. channel-registry (../../../protocol/channel-registry/SKILL.md) is the sole writer of memory/channels/. An advocate becoming a **paid** creator leaves this program: creator-registry (../../../protocol/creator-registry/SKILL.md) record plus contract-helper (../../../influencer/activate/contract-helper/SKILL.md) terms first. Paid creator campaigns are campaign-planner (../../../influencer/target/campaign-planner/SKILL.md). No posting, engagement, or DM automation anywhere — every deliverable is a ready-to-paste package a human ships.

Use when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规

Advocacy Program Designer

Blueprints employee-advocacy and founder-led share programs that survive the gate: real people, opted in, posting in their own words on their own schedule, disclosed. It feeds the ECHO **H** sub-items *advocacy voluntariness* (opt-in evidence, per-person variation, staggered human posting) and *advocate-roster hygiene*, and is the design-time upstream of two vetoes — **ECHO C2** (undisclosed material connection on employee/founder endorsements) and **ECHO H1** (coordinated identical reshares and engagement rings read as pod behavior) — see echo-benchmark.md (../../../references/echo-benchmark.md). Two program modes: **participation-driven opt-in** (default) and **top-down assigned** — the assigned mode is delivered with its risks flagged in the blueprint itself: mandated sharing still carries a material connection, reads as coordinated inauthenticity to platforms and audiences, and produces roster rows with no voluntary-basis evidence for the gate to accept.

**Scope guard**: this skill designs the program and the kits only. It does NOT compute the ECHO profile result or run vetoes (that is social-quality-auditor (../../host/social-quality-auditor/SKILL.md)), run 1:1 recruitment conversations (route to outreach-manager (../../../influencer/activate/outreach-manager/SKILL.md)), or hold canonical person records — saved roster rows are minimal (advocate_ref, disclosure line, opt-in date, voluntary-basis evidence) and go to memory/events/channels.ndjson via an authorized operation: propose request to registry-events.py only; raw handles remain transient resolver/connector input. channel-registry (../../../protocol/channel-registry/SKILL.md) is the sole writer of memory/channels/. An advocate becoming a **paid** creator leaves this program: creator-registry (../../../protocol/creator-registry/SKILL.md) record plus contract-helper (../../../influencer/activate/contract-helper/SKILL.md) terms first. Paid creator campaigns are campaign-planner (../../../influencer/target/campaign-planner/SKILL.md). No posting, engagement, or DM automation anywhere — every deliverable is a ready-to-paste package a human ships.

Quick Start