Gh launch post

Skill aymandakirgh/ghclaudetoolkit/skills/gh-launch-post

Use when the user wants to announce or launch something publicly and asks for an X/Twitter thread, a single tweet, a Show HN post, or launch copy. Triggers on "write a launch thread", "X thread", "tweet this", "Show HN", "Hacker News post", "launch post", "announce this repo", "post about the launch", "ship announcement", "social copy for the launch". Writes in a builder-at-GH voice (a builder shipping, not a founder), keeps OSS unbranded, English and public, uses real numbers only, bans hype words (synergy, 10x, game-changer), and caps cadence at 3 posts per day.From its SKILL.md

Install

npx -y skills add aymandakirgh/ghclaudetoolkit --skill gh-launch-post

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, as published. Nobody here has run it

gh-launch-post

Produce public launch copy — an X thread, a single standalone tweet, and a Show HN post — for a ship. Builds on gh-brand-voice; this skill adds the launch formats and platform rules.

Voice for launches

Builder-at-GH, not founder. Write as the person who built and shipped it. First person is fine ("I built…", "shipped…"). Never claim founder/CEO status or speak for the company.
Unbranded for OSS. Open-source tools are presented on their own merits — no GH logo-drop, no corporate framing. The work speaks; the brand stays out of the way.
English, public. All launch copy is EN.
Real numbers only. Stars, benchmark times, file counts, install commands — only what's true and checkable. No invented traction.
Banned words: synergy, 10x, game-changer (and hype variants). See gh-brand-voice.

Deliverables (produce all three unless told otherwise)

1. X thread (3–7 posts)

Post 1 = the hook + the what. One concrete sentence: what it is and the single best reason to care. No "excited to announce". Lead with the result or the demo.
Middle posts — one idea each: the problem, how it behaves (not a how-to lecture), a real number or a short code/CLI snippet, who it's for.
Last post — where to get it (repo/install line) and a low-key ask (try it / feedback).
Each post ≤ 280 chars. Number them only if it helps; prefer natural flow.

2. Single tweet

A standalone version that works with zero thread context: hook + what + link, ≤ 280 chars. This is the one to pin or reuse.

3. Show HN

Title: Show HN: <name> – <plain one-line description> (no hype, no emoji).
Body: 2–4 short paragraphs — what it does, why you built it, what's notable technically, and an honest note on limitations/what's next. HN rewards candor and dislikes marketing; write for builders. Link the repo.

Cadence rule

Max 3 posts per day. When planning a sequence, schedule across days; never dump more than three public posts in a single day. If the user asks for more, push back and spread them out.

Quality bar before handing over

Hook earns the click without hype or banned words.
Every number is real; remove anything you can't verify.
Voice is builder, not founder; OSS stays unbranded.
Show HN reads honest (includes a real limitation), not like an ad.
Cadence ≤ 3/day if a schedule is implied.

Output the three deliverables clearly separated, plus a one-line suggested posting schedule that respects the 3/day cap.