- THE COMPLIANCE MODE IS LAW. The caller passes a per-platform mode (
references/compliance-modes.md);
it overrides every default. If the mode forbids vote mobilization (e.g. Hacker News), do NOT produce
supporter-wave plans or "we're live, come engage" broadcasts — coach presence-in-thread only. Never
produce copy that violates the platform's rules.
- NEVER SOLICIT OR INCENTIVIZE VOTES. No "please upvote", "support us", "give us a vote", "help us hit
#1", and never tie any discount/perk to a vote. Ask people to visit, try, and give honest feedback.
Every message passes the banned-phrase scan in
references/compliance-modes.md before it ships.
- PERSONALIZE; DON'T SPAM. 1:1 DMs go only to people the user actually knows, personalized each time.
Identical copy-pasted blasts to strangers and scraped cold emails are prohibited "mass messaging".
Opt-in waitlist/customer email framed for feedback is fine; cold mass-DM is not.
- GROUND IT IN THE REAL PRODUCT. Read
.ulpi/launch/positioning.md if present; if it's missing (e.g. run
standalone before a platform skill produced it), gather the product summary from the caller or via one
or two focused questions. Never invent features or proof.
- BE HONEST ABOUT REACH. If the user has little or no audience, say so plainly and coach building one —
don't imply outreach can manufacture a result it can't.
- STAGGER, DON'T BLAST (when the mode allows waves). Notify in waves across the day to sustain genuine
velocity; a single mass spike both underperforms and looks like manipulation.
launch-outreach
Inputs
$request: the platform/launch and the audience/channels available. When invoked by a launch skill,
the caller passes the compliance mode, the product (positioning.md), and the launch date/time.
Standalone, gather these with one or two focused questions.
Goal
Produce a segmented outreach plan + paste-ready, compliant messages for the launch, written to
.ulpi/launch/<channel>/OUTREACH.md (the <channel> is the hyphenated launch slug the caller passes, e.g.
product-hunt; or handed back to the caller). Covers recruiting the audience
before launch and notifying it on the day, in the platform's compliance mode.
Step 0: Resolve context & compliance mode
Adopt the caller's compliance mode, or pick it from references/compliance-modes.md by platform. Confirm
the product, the launch date/time (timezone), and what audience/channels exist. Success criteria: the
mode, product, date, and available reach are known.
Step 1: Recruit / assess the audience (pre-launch)
Load references/outreach-playbook.md. If there's runway before launch, coach building a warm list
off-platform (a simple email-capture landing page + building-in-public on X/LinkedIn) — many platforms
no longer offer a native pre-launch notify list. Inventory what the user already has (list size, social
following, communities they're a real member of, existing users). Be realistic about what that reach
can produce. Success criteria: an honest picture of available reach and a plan to grow it if there's time.
Step 2: Segment & plan reach
Segment the audience and decide how each is reached (load references/outreach-playbook.md):
- Team / co-founders — briefed, on-call.
- Friends & peers — personal, low-pressure heads-up.
- Existing users / customers / waitlist — highest intent; a genuine "we're live, tell us what to fix".
- Communities you're a real member of — a single organic heads-up where allowed, never a vote drive.
- Public audience (X/LinkedIn followers) — launch-day posts.
DM the top ~20–50 supporters personally (personalized each time); reach the rest via segmented email
and broadcast posts. Success criteria: each segment has a channel, a message type, and a send time.
Step 3: Draft the message set (grounded + compliant)
Load references/templates.md. Draft, personalized to the product from positioning.md, in the
compliance mode: the pre-launch teaser DM, the waitlist "we launch soon, I'd love your honest feedback"
email, the launch-day email wave(s), the community heads-up, the personal 1:1 DM, and the social
amplification posts (X thread, LinkedIn). Every message asks for a visit / try / feedback, never a
vote. Success criteria: every message is paste-ready, personalized, and on-mode.
Step 4: Wave plan (only if the mode allows mobilization)
If the compliance mode allows supporter waves (e.g. Product Hunt), lay out a staggered send schedule
across the launch day (closest circle first, then list waves by engagement/timezone, holding a reserve for
the midday lull and final hours) so velocity is sustained, not spiked. If the mode forbids mobilization
(e.g. Hacker News), skip this and coach genuine in-thread presence instead. Success criteria: a
wave schedule that fits the mode — or a clear note that waves don't apply here.
Step 5: Compliance scan
Run the banned-phrase scan (references/compliance-modes.md) over every message. Any hit → rewrite.
Success criteria: zero vote-soliciting/incentivizing/mass-spam language anywhere.
Guardrails
- The compliance mode overrides all defaults; when unsure, ask the caller.
- Never solicit or incentivize votes; never tie a perk to a vote.
- Personalize 1:1 outreach; no identical blasts to strangers, no scraped cold email.
- Ground messages in the real product; reuse
.ulpi/launch/positioning.md.
- Be honest about reach; don't imply outreach can fake momentum.
- Respect each community's self-promo rules; share only where the user genuinely participates.
- This skill writes person-to-person and broadcast outreach — not the listing/first-comment copy (that's
launch-copy).
When To Load References
references/outreach-playbook.md — recruiting an audience, the five segments, reach plan, and the
wave strategy with timing (Steps 1, 2, 4).
references/templates.md — the paste-ready, compliant message library: teaser DM, waitlist email,
launch-day email waves, community heads-up, 1:1 DM, X thread, LinkedIn post (Step 3).
references/compliance-modes.md — per-platform compliance dials and the banned-phrase scan
(Steps 0, 5).
Output Contract
Write / return:
- an
OUTREACH.md with the segmented plan and the paste-ready, compliant messages per segment
- (if the mode allows) a staggered launch-day wave schedule; otherwise a note that waves don't apply
- the compliance affirmation: zero vote-soliciting/incentivizing/mass-spam language, scan passed
1---
2name: launch-outreach
3version: 1.0.0
4description: |
5 Build and notify a launch's supporter audience with paste-ready, platform-COMPLIANT outreach — the
6 messages you send to PEOPLE, never the on-listing copy. Recruits an audience before launch, segments it
7 (team · friends · users/waitlist · communities · public followers), and notifies it in timed waves on the
8 day. Drafts the teaser DMs, waitlist and launch-day emails, community heads-ups, 1:1 DMs, and X/LinkedIn
9 amplification posts, and writes them to `.ulpi/launch/<channel>/OUTREACH.md`. Parameterized by a
10 per-platform COMPLIANCE MODE the caller passes (Product Hunt: supporter waves allowed, ask for feedback not
11 upvotes; Hacker News: NO vote mobilization at all); grounds every message in `.ulpi/launch/positioning.md`
12 and NEVER solicits/incentivizes votes or mass-spams. Shared audience block of the launch-* family, invoked
13 by the per-platform runners (`launch-product-hunt`, `launch-hacker-news`, `launch-x`, `launch-linkedin`) or
14 run standalone. Use when a launch needs who-to-tell and what-to-say, compliant to each platform's rules.
15allowed-tools:
16 - AskUserQuestion
17 - Read
18 - Write
19argument-hint: "[platform + audience to reach, e.g. 'Product Hunt launch, ~200 email + X']"
20arguments:
21 - request
22when_to_use: |
23 Use when planning who to tell about a launch and what to say — recruiting a pre-launch audience, segmenting
24 supporters, and drafting compliant DMs/emails/community posts/social broadcasts. Examples: "who do I notify
25 for my launch and what do I say", "draft my launch-day emails", "write the supporter outreach without
26 breaking the rules". Also invoked by the platform runners, which pass a compliance mode. Do NOT use to
27 write the listing copy — tagline, description, first comment (redirect to `launch-copy`) — and do NOT use
28 to manipulate votes; this skill refuses that.
29effort: high
30metadata:
31 source: https://skillmd.com/skills/ulpi-io/launch-outreach
32---
33
34<EXTREMELY-IMPORTANT>
35This skill drafts outreach for a launch. Non-negotiable rules:
36
371. THE COMPLIANCE MODE IS LAW. The caller passes a per-platform mode (`references/compliance-modes.md`);
38 it overrides every default. If the mode forbids vote mobilization (e.g. Hacker News), do NOT produce
39 supporter-wave plans or "we're live, come engage" broadcasts — coach presence-in-thread only. Never
40 produce copy that violates the platform's rules.
412. NEVER SOLICIT OR INCENTIVIZE VOTES. No "please upvote", "support us", "give us a vote", "help us hit
42 #1", and never tie any discount/perk to a vote. Ask people to **visit, try, and give honest feedback**.
43 Every message passes the banned-phrase scan in `references/compliance-modes.md` before it ships.
443. PERSONALIZE; DON'T SPAM. 1:1 DMs go only to people the user actually knows, personalized each time.
45 Identical copy-pasted blasts to strangers and scraped cold emails are prohibited "mass messaging".
46 Opt-in waitlist/customer email framed for feedback is fine; cold mass-DM is not.
474. GROUND IT IN THE REAL PRODUCT. Read `.ulpi/launch/positioning.md` if present; if it's missing (e.g. run
48 standalone before a platform skill produced it), gather the product summary from the caller or via one
49 or two focused questions. Never invent features or proof.
505. BE HONEST ABOUT REACH. If the user has little or no audience, say so plainly and coach building one —
51 don't imply outreach can manufacture a result it can't.
526. STAGGER, DON'T BLAST (when the mode allows waves). Notify in waves across the day to sustain genuine
53 velocity; a single mass spike both underperforms and looks like manipulation.
54</EXTREMELY-IMPORTANT>
55
56# launch-outreach
57
58## Inputs
59
60- `$request`: the platform/launch and the audience/channels available. When invoked by a launch skill,
61 the caller passes the **compliance mode**, the product (`positioning.md`), and the launch date/time.
62 Standalone, gather these with one or two focused questions.
63
64## Goal
65
66Produce a **segmented outreach plan + paste-ready, compliant messages** for the launch, written to
67`.ulpi/launch/<channel>/OUTREACH.md` (the `<channel>` is the hyphenated launch slug the caller passes, e.g.
68`product-hunt`; or handed back to the caller). Covers recruiting the audience
69before launch and notifying it on the day, in the platform's compliance mode.
70
71## Step 0: Resolve context & compliance mode
72
73Adopt the caller's compliance mode, or pick it from `references/compliance-modes.md` by platform. Confirm
74the product, the launch date/time (timezone), and what audience/channels exist. **Success criteria**: the
75mode, product, date, and available reach are known.
76
77## Step 1: Recruit / assess the audience (pre-launch)
78
79Load `references/outreach-playbook.md`. If there's runway before launch, coach building a warm list
80**off-platform** (a simple email-capture landing page + building-in-public on X/LinkedIn) — many platforms
81no longer offer a native pre-launch notify list. Inventory what the user already has (list size, social
82following, communities they're a real member of, existing users). **Be realistic** about what that reach
83can produce. **Success criteria**: an honest picture of available reach and a plan to grow it if there's time.
84
85## Step 2: Segment & plan reach
86
87Segment the audience and decide how each is reached (load `references/outreach-playbook.md`):
88
891. **Team / co-founders** — briefed, on-call.
902. **Friends & peers** — personal, low-pressure heads-up.
913. **Existing users / customers / waitlist** — highest intent; a genuine "we're live, tell us what to fix".
924. **Communities** you're a real member of — a single organic heads-up where allowed, never a vote drive.
935. **Public audience** (X/LinkedIn followers) — launch-day posts.
94
95**DM the top ~20–50 supporters personally** (personalized each time); reach the rest via segmented email
96and broadcast posts. **Success criteria**: each segment has a channel, a message type, and a send time.
97
98## Step 3: Draft the message set (grounded + compliant)
99
100Load `references/templates.md`. Draft, personalized to the product from `positioning.md`, in the
101compliance mode: the pre-launch teaser DM, the waitlist "we launch soon, I'd love your honest feedback"
102email, the launch-day email wave(s), the community heads-up, the personal 1:1 DM, and the social
103amplification posts (X thread, LinkedIn). Every message asks for a **visit / try / feedback**, never a
104vote. **Success criteria**: every message is paste-ready, personalized, and on-mode.
105
106## Step 4: Wave plan (only if the mode allows mobilization)
107
108If the compliance mode allows supporter waves (e.g. Product Hunt), lay out a **staggered send schedule**
109across the launch day (closest circle first, then list waves by engagement/timezone, holding a reserve for
110the midday lull and final hours) so velocity is sustained, not spiked. If the mode forbids mobilization
111(e.g. Hacker News), **skip this** and coach genuine in-thread presence instead. **Success criteria**: a
112wave schedule that fits the mode — or a clear note that waves don't apply here.
113
114## Step 5: Compliance scan
115
116Run the banned-phrase scan (`references/compliance-modes.md`) over every message. Any hit → rewrite.
117**Success criteria**: zero vote-soliciting/incentivizing/mass-spam language anywhere.
118
119## Guardrails
120
121- The compliance mode overrides all defaults; when unsure, ask the caller.
122- Never solicit or incentivize votes; never tie a perk to a vote.
123- Personalize 1:1 outreach; no identical blasts to strangers, no scraped cold email.
124- Ground messages in the real product; reuse `.ulpi/launch/positioning.md`.
125- Be honest about reach; don't imply outreach can fake momentum.
126- Respect each community's self-promo rules; share only where the user genuinely participates.
127- This skill writes person-to-person and broadcast outreach — not the listing/first-comment copy (that's
128 `launch-copy`).
129
130## When To Load References
131
132- `references/outreach-playbook.md` — recruiting an audience, the five segments, reach plan, and the
133 wave strategy with timing (Steps 1, 2, 4).
134- `references/templates.md` — the paste-ready, compliant message library: teaser DM, waitlist email,
135 launch-day email waves, community heads-up, 1:1 DM, X thread, LinkedIn post (Step 3).
136- `references/compliance-modes.md` — per-platform compliance dials and the banned-phrase scan
137 (Steps 0, 5).
138
139## Output Contract
140
141Write / return:
142
1431. an `OUTREACH.md` with the segmented plan and the paste-ready, compliant messages per segment
1442. (if the mode allows) a staggered launch-day wave schedule; otherwise a note that waves don't apply
1453. the compliance affirmation: zero vote-soliciting/incentivizing/mass-spam language, scan passed