mirror of
https://github.com/ulpi-io/skills.git
synced 2026-09-19 03:35:17 +08:00
Ciprian Spiridon
26d681801b
Extends the launch-* family to X (Twitter) and LinkedIn — own-audience social
launches — grounded in current sources and reviewed across multiple adversarial
rounds (9 findings fixed, 0 blockers/highs; facts independently re-confirmed clean).
New skills:
- launch-x — X launch orchestrator: writes .ulpi/launch/x/ (POST thread, PLAN
golden-hour runbook, OUTREACH, CHECKLIST, analytics). The link goes in a REPLY,
not the main tweet (link-in-body reach penalty); golden-hour replies are the top
lever (X's open-source code: a reply the author replies back to = 75.0, the
highest positive signal); X Premium is ~table-stakes for reach (Buffer's 18.8M-
post study, third-party). Phoenix (xAI, Jan 2026) replaced the heavy-ranker, so
2026 weights are labeled non-official.
- launch-linkedin — LinkedIn launch orchestrator: writes .ulpi/launch/linkedin/.
Problem-first hook (survives the ~140-char mobile "see more" fold), link in the
FIRST COMMENT (it's the preview card that hurts, and the penalty is contested/
smaller in 2026 — don't over-engineer), dwell-time-first (an officially confirmed
signal). Sanctioned team amplification ("Notify Employees") vs banned engagement
pods + engagement-bait (both official violations).
Unlike Product Hunt / Hacker News, these are own-audience posts with NO vote-
manipulation rule — you MAY ask your audience and team to genuinely engage. The
compliance work shifts to platform-penalized anti-patterns: engagement-bait,
bought/coordinated engagement / pods, and the link-in-body reach penalty.
Shared: launch-copy gains x + linkedin asset profiles; launch-outreach gains
x + linkedin engagement-allowed compliance modes + the engagement-bait scan.
README adds rows + sections for both. Each composes launch-copy / launch-outreach
/ launch-analytics with graceful fallback.