- KEEP A LINK-PREVIEW CARD OUT OF THE POST BODY. Put the launch link in the first comment (and say
"link in the comments") — the low-risk default. The reach hit is mainly on the rich preview card, and
the link penalty is contested/smaller in 2026 (see
references/li-format-rules.md); don't over-engineer
it — a native, dwell-worthy post matters more.
- WIN THE HOOK. Only the first
2 lines (140–210 chars) show before "…see more" — that hook decides who
expands. Lead with the strongest concrete line; no "I'm excited to announce…" throat-clearing.
- ENGAGEMENT IS ALLOWED — BAIT IS NOT. You MAY ask your network and team to engage genuinely (employee
amplification is fine and effective); there is no vote-ring rule. But never use engagement-bait that
LinkedIn demotes ("comment YES below", "tag 3 people"), never use engagement pods, and don't buy
engagement. Coach genuine asks.
- DON'T EDIT RIGHT AFTER POSTING. Editing a post in the first ~hour can suppress its reach — proof the
post (and the first comment) BEFORE publishing.
- GROUND EVERY WORD IN THE REAL PRODUCT. Read
.ulpi/launch/positioning.md if present, else the README,
the live site (via browse), and the repo. Never invent features or metrics.
- WIN THE GOLDEN HOUR. Early engagement (~first 60–90 min) decides reach — be present and reply to every
comment fast, with substance. Bake this into
PLAN.md.
- COMPOSE THE SHARED SKILLS, DEGRADE GRACEFULLY. Invoke
launch-copy (LinkedIn asset profile),
launch-outreach (mode linkedin), and launch-analytics (source linkedin). If a companion isn't
installed, give the one-line install (npx skills add https://github.com/ulpi-io/skills --skill <name>)
and fall back to the built-in reference — never hard-fail. Run the pre-flight gate
(references/preflight-gate.md) before posting, and WRITE the package to disk under
.ulpi/launch/linkedin/.
launch-linkedin
Inputs
$request: the product to launch, or a specific LinkedIn goal (e.g. "write the post", "plan launch
day"), plus optional links (live URL, demo, media).
Goal
Produce a paste-ready LinkedIn launch package under .ulpi/launch/linkedin/ (+ the shared
.ulpi/launch/positioning.md):
POST.md — the launch post: the hook (first ~2 lines), the skimmable body, the format/media plan,
hashtags, and the product link as the first comment (UTM-tagged).
PLAN.md — when to post, the golden-hour engagement runbook, team amplification, and the post-launch plan.
CHECKLIST.md — the pre-flight gate.
Step 0: Discovery & companions
Resolve, asking only what you can't determine: the product (what it does, who for, live URL, demo/media);
whether it posts from a personal profile (usually higher reach) or the company page; the user's
network/team who'll engage. Note which companion skills are installed (launch-copy, launch-outreach,
launch-analytics); install-hint if missing, but proceed. Success criteria: product, posting identity,
and reach are known.
Step 1: Ground the product → .ulpi/launch/positioning.md
Reuse .ulpi/launch/positioning.md if present; else build it from the README, the live site (via
browse), the repo, and project-context.md/.ulpi/design. Distill: one-line what-it-is, ICP, core
value, top 3 differentiators, proof points, links — nothing invented. Save it as the shared source of
truth. Success criteria: a brief no line will contradict.
Step 2: Mechanics, timing & targets
Load references/li-mechanics.md. Decide and record (into PLAN.md): when to post (a weekday morning
window the user can attend live), realistic reach expectations, and the format that fits (text+image,
native document/carousel, or native video — the higher-reach formats). Success criteria: a concrete
post time, a chosen format, and an honest reach target.
Step 3: Write the post → POST.md
Hand the LinkedIn asset profile (references/li-format-rules.md + references/post-copy.md) to the
launch-copy skill to draft the hook (first ~2 lines before "…see more") and the post body
(hook → story/problem → what we built → proof → CTA), in a professional-but-human voice — no hype. Fallback:
if launch-copy isn't installed, draft from those references. Then LinkedIn-owned: assemble POST.md with
the formatted post (line breaks for skimmability), the format/media plan, 3–5 niche hashtags, the
tags (people/company page), and the product link as the first comment (write it with
utm_source=linkedin and a <launch> campaign placeholder — Step 6 finalizes the scheme and back-fills the
exact tagged URL). Success criteria: a hook that earns the expand, link in the first comment not the
body — paste-ready.
Step 4: Plan timing & engagement → PLAN.md
Load references/li-mechanics.md and references/timing-engagement.md. Write into PLAN.md: the post
time, the golden-hour runbook (post → add the link as the first comment → reply to every comment with
substance in the first ~60–90 min → don't edit the post → keep it alive), and the post-launch plan
(repurpose, follow up). Success criteria: the user knows exactly when to post and how to run the first
90 minutes.
Step 5: Cross-promotion & team amplification → OUTREACH.md
Invoke the launch-outreach skill with compliance mode linkedin, positioning.md, and the post
time — it writes .ulpi/launch/linkedin/OUTREACH.md with the genuine, compliant asks: notify your email
list / other channels, ask your team/employees to engage early (employee amplification, genuine — not a
pod), and a few personal shares. Fallback: if it isn't installed, draft these to
.ulpi/launch/linkedin/OUTREACH.md yourself from references/antipatterns-compliance.md
(engagement-allowed, bait-free). Success criteria: paste-ready, genuine engagement asks in
OUTREACH.md — zero engagement-bait or pods.
Step 6: Wire measurement → tag links & events
Invoke the launch-analytics skill — channel linkedin (output dir) with utm_source
linkedin (GA value) — to UTM-tag the product link (the one in the first comment) and wire signup/
activation tracking, writing .ulpi/launch/linkedin/analytics.md. Then update POST.md: replace the
first-comment placeholder link with the final UTM-tagged URL so POST.md and analytics.md match.
Fallback: if launch-analytics isn't installed, write a minimal .ulpi/launch/linkedin/analytics.md
yourself — the UTM scheme (utm_source=linkedin&utm_medium=launch-post&utm_campaign=<launch>), the tagged
link, and brief signup/activation notes — so the artifact exists either way. Success criteria: the link
is attributable and signups are trackable — not just reactions.
Step 7: Pre-flight gate → CHECKLIST.md
Run references/preflight-gate.md end to end and write the result into CHECKLIST.md: hook earns the
expand (counted ≤ the see-more cut), link is in the first comment (not the body), format chosen, hashtags
3–5, zero engagement-bait/pods, link UTM-tagged, post proofed (won't be edited after), post time set,
golden-hour availability blocked. Fix any failing box and re-run. Success criteria: every box ticked.
Step 8: Post-launch plan → append to PLAN.md
Load references/timing-engagement.md (post-launch section): keep replying with substance through the
day, repost/repurpose into other channels, follow up with new connections, and reuse the post as social
proof. Success criteria: the user knows what to do after the golden hour.
Guardrails
- Keep the external link out of the post body — link in the first comment; UTM-tag it.
- Win the hook (≤ the see-more cut); never open with "I'm excited to announce…".
- Don't edit the post right after publishing; proof it first.
- Engagement asks are fine; engagement-bait, pods, and bought engagement are not.
- Ground all copy in the real product; never invent features or metrics.
- Compose the shared skills; if one is absent, install-hint + fall back — never hard-fail.
- Write the package to disk; don't leave it as ephemeral chat.
When To Load References
references/li-mechanics.md — the algorithm, dwell time, comments-over-reactions, the link penalty,
the golden hour, the edit penalty, realistic outcomes (Steps 2, 4).
references/li-format-rules.md — char limit, the see-more hook, formats that earn reach, hashtags, the
link-in-first-comment tactic (Step 3).
references/post-copy.md — the LinkedIn asset profile passed to launch-copy, the hook + post skeleton,
and the inline copy fallback (Step 3).
references/timing-engagement.md — post timing, the golden-hour runbook, team amplification, and the
post-launch section (Steps 4, 8).
references/antipatterns-compliance.md — what LinkedIn penalizes, the engagement-bait/pod line, and the
engagement-ask fallback (Steps 5, 7).
references/preflight-gate.md — the blocking readiness gate (Step 7).
Output Contract
Write under .ulpi/launch/ and report:
.ulpi/launch/positioning.md — the shared grounded brief (created or reused)
linkedin/POST.md — the hook, the post body, the format/media plan, hashtags, the link as a UTM-tagged
first comment
linkedin/PLAN.md — the post time, the golden-hour runbook, the post-launch plan
linkedin/CHECKLIST.md — the pre-flight gate result (every box ticked)
linkedin/OUTREACH.md — the cross-promo / team-amplification asks (from launch-outreach, mode linkedin)
linkedin/analytics.md — UTM map + signup/activation tracking (from launch-analytics)
- a report of which companion skills were used vs fell back to built-ins
1---
2name: launch-linkedin
3version: 1.0.0
4description: |
5 Prepare and run a product/company launch on LinkedIn end to end — the launch link goes in the FIRST
6 COMMENT, not the post body, and you never edit the post right after publishing. Grounds in the real
7 product, then writes a paste-ready package to `.ulpi/launch/linkedin/`: `POST.md` (the launch **post** — a
8 strong hook in the first ~2 lines before the "…see more" cut, a skimmable body, the reach-earning format,
9 hashtags, and the product link as the **first comment**), `PLAN.md` (timing, the **golden-hour** engagement
10 runbook, team amplification, and the post-launch plan), and `CHECKLIST.md` (a blocking pre-flight gate). The
11 LinkedIn runner of the launch-* family: it owns LinkedIn mechanics, format rules, and the gate, and
12 composes the shared `launch-copy` (post copy), `launch-outreach` (team amplification, mode `linkedin`), and
13 `launch-analytics` (UTM + conversion tracking), degrading to built-in fallbacks if a companion isn't
14 installed. Reads the shared `.ulpi/launch/positioning.md`. Engagement asks to your network and team are
15 fine (no vote-ring rules), but it avoids what LinkedIn penalizes — a link-preview card in the body,
16 engagement-bait, pods, and an early edit. Use when the user wants a LinkedIn launch post written and launch
17 day planned.
18allowed-tools:
19 - AskUserQuestion
20 - Read
21 - Write
22 - Skill
23argument-hint: "[product or LinkedIn launch goal]"
24arguments:
25 - request
26when_to_use: |
27 Use when the user wants to launch a product or company on LinkedIn, write a launch post, or plan launch-day
28 engagement. Examples: "write my LinkedIn launch post", "plan my LinkedIn launch", "help me announce on
29 LinkedIn". For an X / Twitter launch use `launch-x`, for Product Hunt use `launch-product-hunt`, for Hacker
30 News use `launch-hacker-news`. Do NOT use for the post copy alone (redirect to `launch-copy`) or the
31 cross-channel supporter messages alone (`launch-outreach`) — this runs the whole LinkedIn launch and
32 composes those.
33effort: high
34metadata:
35 source: https://skillmd.com/skills/ulpi-io/launch-linkedin
36---
37
38<EXTREMELY-IMPORTANT>
39This skill prepares and coaches a LinkedIn launch. Non-negotiable rules:
40
411. KEEP A LINK-PREVIEW CARD OUT OF THE POST BODY. Put the launch link in the **first comment** (and say
42 "link in the comments") — the low-risk default. The reach hit is mainly on the rich preview *card*, and
43 the link penalty is contested/smaller in 2026 (see `references/li-format-rules.md`); don't over-engineer
44 it — a native, dwell-worthy post matters more.
452. WIN THE HOOK. Only the first ~2 lines (~140–210 chars) show before "…see more" — that hook decides who
46 expands. Lead with the strongest concrete line; no "I'm excited to announce…" throat-clearing.
473. ENGAGEMENT IS ALLOWED — BAIT IS NOT. You MAY ask your network and team to engage genuinely (employee
48 amplification is fine and effective); there is no vote-ring rule. But never use engagement-bait that
49 LinkedIn demotes ("comment YES below", "tag 3 people"), never use engagement pods, and don't buy
50 engagement. Coach genuine asks.
514. DON'T EDIT RIGHT AFTER POSTING. Editing a post in the first ~hour can suppress its reach — proof the
52 post (and the first comment) BEFORE publishing.
535. GROUND EVERY WORD IN THE REAL PRODUCT. Read `.ulpi/launch/positioning.md` if present, else the README,
54 the live site (via `browse`), and the repo. Never invent features or metrics.
556. WIN THE GOLDEN HOUR. Early engagement (~first 60–90 min) decides reach — be present and reply to every
56 comment fast, with substance. Bake this into `PLAN.md`.
577. COMPOSE THE SHARED SKILLS, DEGRADE GRACEFULLY. Invoke `launch-copy` (LinkedIn asset profile),
58 `launch-outreach` (mode `linkedin`), and `launch-analytics` (source `linkedin`). If a companion isn't
59 installed, give the one-line install (`npx skills add https://github.com/ulpi-io/skills --skill <name>`)
60 and fall back to the built-in reference — never hard-fail. Run the pre-flight gate
61 (`references/preflight-gate.md`) before posting, and WRITE the package to disk under
62 `.ulpi/launch/linkedin/`.
63</EXTREMELY-IMPORTANT>
64
65# launch-linkedin
66
67## Inputs
68
69- `$request`: the product to launch, or a specific LinkedIn goal (e.g. "write the post", "plan launch
70 day"), plus optional links (live URL, demo, media).
71
72## Goal
73
74Produce a paste-ready LinkedIn launch package under `.ulpi/launch/linkedin/` (+ the shared
75`.ulpi/launch/positioning.md`):
76
77- `POST.md` — the launch **post**: the hook (first ~2 lines), the skimmable body, the format/media plan,
78 hashtags, and the product link as the **first comment** (UTM-tagged).
79- `PLAN.md` — when to post, the golden-hour engagement runbook, team amplification, and the post-launch plan.
80- `CHECKLIST.md` — the pre-flight gate.
81
82## Step 0: Discovery & companions
83
84Resolve, asking only what you can't determine: the product (what it does, who for, live URL, demo/media);
85whether it posts from a **personal profile** (usually higher reach) or the **company page**; the user's
86network/team who'll engage. Note which companion skills are installed (`launch-copy`, `launch-outreach`,
87`launch-analytics`); install-hint if missing, but proceed. **Success criteria**: product, posting identity,
88and reach are known.
89
90## Step 1: Ground the product → `.ulpi/launch/positioning.md`
91
92Reuse `.ulpi/launch/positioning.md` if present; else build it from the README, the live site (via
93`browse`), the repo, and `project-context.md`/`.ulpi/design`. Distill: one-line what-it-is, ICP, core
94value, top 3 differentiators, proof points, links — nothing invented. Save it as the shared source of
95truth. **Success criteria**: a brief no line will contradict.
96
97## Step 2: Mechanics, timing & targets
98
99Load `references/li-mechanics.md`. Decide and record (into `PLAN.md`): **when to post** (a weekday morning
100window the user can attend live), realistic reach expectations, and the **format** that fits (text+image,
101native document/carousel, or native video — the higher-reach formats). **Success criteria**: a concrete
102post time, a chosen format, and an honest reach target.
103
104## Step 3: Write the post → `POST.md`
105
106Hand the **LinkedIn asset profile** (`references/li-format-rules.md` + `references/post-copy.md`) to the
107**`launch-copy`** skill to draft the **hook** (first ~2 lines before "…see more") and the **post body**
108(hook → story/problem → what we built → proof → CTA), in a professional-but-human voice — no hype. *Fallback:*
109if `launch-copy` isn't installed, draft from those references. Then LinkedIn-owned: assemble `POST.md` with
110the formatted post (line breaks for skimmability), the **format/media plan**, **3–5 niche hashtags**, the
111tags (people/company page), and the **product link as the first comment** (write it with
112`utm_source=linkedin` and a `<launch>` campaign placeholder — Step 6 finalizes the scheme and back-fills the
113exact tagged URL). **Success criteria**: a hook that earns the expand, link in the first comment not the
114body — paste-ready.
115
116## Step 4: Plan timing & engagement → `PLAN.md`
117
118Load `references/li-mechanics.md` and `references/timing-engagement.md`. Write into `PLAN.md`: the **post
119time**, the **golden-hour runbook** (post → add the link as the first comment → reply to every comment with
120substance in the first ~60–90 min → don't edit the post → keep it alive), and the post-launch plan
121(repurpose, follow up). **Success criteria**: the user knows exactly when to post and how to run the first
12290 minutes.
123
124## Step 5: Cross-promotion & team amplification → `OUTREACH.md`
125
126Invoke the **`launch-outreach`** skill with compliance mode **`linkedin`**, `positioning.md`, and the post
127time — it writes `.ulpi/launch/linkedin/OUTREACH.md` with the genuine, compliant asks: notify your email
128list / other channels, ask your team/employees to engage early (employee amplification, genuine — not a
129pod), and a few personal shares. *Fallback:* if it isn't installed, draft these to
130`.ulpi/launch/linkedin/OUTREACH.md` yourself from `references/antipatterns-compliance.md`
131(engagement-allowed, bait-free). **Success criteria**: paste-ready, genuine engagement asks in
132`OUTREACH.md` — zero engagement-bait or pods.
133
134## Step 6: Wire measurement → tag links & events
135
136Invoke the **`launch-analytics`** skill — **channel `linkedin`** (output dir) with **`utm_source`
137`linkedin`** (GA value) — to UTM-tag the product link (the one in the first comment) and wire signup/
138activation tracking, writing `.ulpi/launch/linkedin/analytics.md`. Then **update `POST.md`**: replace the
139first-comment placeholder link with the final UTM-tagged URL so `POST.md` and `analytics.md` match.
140*Fallback:* if `launch-analytics` isn't installed, write a minimal `.ulpi/launch/linkedin/analytics.md`
141yourself — the UTM scheme (`utm_source=linkedin&utm_medium=launch-post&utm_campaign=<launch>`), the tagged
142link, and brief signup/activation notes — so the artifact exists either way. **Success criteria**: the link
143is attributable and signups are trackable — not just reactions.
144
145## Step 7: Pre-flight gate → `CHECKLIST.md`
146
147Run `references/preflight-gate.md` end to end and write the result into `CHECKLIST.md`: hook earns the
148expand (counted ≤ the see-more cut), link is in the first comment (not the body), format chosen, hashtags
1493–5, **zero** engagement-bait/pods, link UTM-tagged, post proofed (won't be edited after), post time set,
150golden-hour availability blocked. Fix any failing box and re-run. **Success criteria**: every box ticked.
151
152## Step 8: Post-launch plan → append to `PLAN.md`
153
154Load `references/timing-engagement.md` (post-launch section): keep replying with substance through the
155day, repost/repurpose into other channels, follow up with new connections, and reuse the post as social
156proof. **Success criteria**: the user knows what to do after the golden hour.
157
158## Guardrails
159
160- Keep the external link out of the post body — link in the first comment; UTM-tag it.
161- Win the hook (≤ the see-more cut); never open with "I'm excited to announce…".
162- Don't edit the post right after publishing; proof it first.
163- Engagement asks are fine; engagement-bait, pods, and bought engagement are not.
164- Ground all copy in the real product; never invent features or metrics.
165- Compose the shared skills; if one is absent, install-hint + fall back — never hard-fail.
166- Write the package to disk; don't leave it as ephemeral chat.
167
168## When To Load References
169
170- `references/li-mechanics.md` — the algorithm, dwell time, comments-over-reactions, the link penalty,
171 the golden hour, the edit penalty, realistic outcomes (Steps 2, 4).
172- `references/li-format-rules.md` — char limit, the see-more hook, formats that earn reach, hashtags, the
173 link-in-first-comment tactic (Step 3).
174- `references/post-copy.md` — the LinkedIn asset profile passed to `launch-copy`, the hook + post skeleton,
175 and the inline copy fallback (Step 3).
176- `references/timing-engagement.md` — post timing, the golden-hour runbook, team amplification, and the
177 post-launch section (Steps 4, 8).
178- `references/antipatterns-compliance.md` — what LinkedIn penalizes, the engagement-bait/pod line, and the
179 engagement-ask fallback (Steps 5, 7).
180- `references/preflight-gate.md` — the blocking readiness gate (Step 7).
181
182## Output Contract
183
184Write under `.ulpi/launch/` and report:
185
1861. `.ulpi/launch/positioning.md` — the shared grounded brief (created or reused)
1872. `linkedin/POST.md` — the hook, the post body, the format/media plan, hashtags, the link as a UTM-tagged
188 first comment
1893. `linkedin/PLAN.md` — the post time, the golden-hour runbook, the post-launch plan
1904. `linkedin/CHECKLIST.md` — the pre-flight gate result (every box ticked)
1915. `linkedin/OUTREACH.md` — the cross-promo / team-amplification asks (from `launch-outreach`, mode `linkedin`)
1926. `linkedin/analytics.md` — UTM map + signup/activation tracking (from `launch-analytics`)
1937. a report of which companion skills were used vs fell back to built-ins