agentsclimarketplace

Show hn launchpad

Skill daewoochen/oss-flywheel-skills/skills/show-hn-launchpad

Practical Codex-compatible skills for README, demos, launches, and OSS growth loops

Install
npx -y skills add daewoochen/oss-flywheel-skills --skill show-hn-launchpad

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

  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Use when a user wants to launch or relaunch a project on Show HN, Product Hunt, X, Reddit, or similar communities. This skill extracts the honest hook, maps it to each channel, and prepares titles, post copy, comment plans, and launch FAQs.

SKILL.md

1.9 KB, as published. Nobody here has run it

Show HN Launchpad

Turn shipped work into a launch kit that feels specific, credible, and easy to reuse across channels.

When to use

  • A new release, side project, or open-source tool is ready to share.
  • The team has built something real but the launch message is fuzzy.
  • A founder or maintainer wants a Show HN post without sounding like an ad.
  • The same release needs tailored copy for multiple communities.

Workflow

  1. Start with the truth.
    • Identify what changed, who it helps, and what is genuinely novel.
    • Find the strongest "why now" angle.
  2. Match the message to the channel.
    • Show HN wants the build story and sharpest demo.
    • Product Hunt wants value, audience, and polished positioning.
    • X wants short hooks and shareable lines.
    • Reddit wants concrete usefulness and less founder energy.
  3. Draft the launch kit.
    • Create 3 to 5 title options.
    • Write the main post body.
    • Prepare likely comments, FAQs, and objections.
  4. Keep it grounded.
    • Prefer specifics, screenshots, and lessons learned.
    • Do not fake demand or write in generic startup voice.
  5. End with a launch checklist.
    • Links, screenshots, maker comment, docs, and fallback answers.

Expected Deliverables

  • Channel-specific title options
  • A primary post draft
  • Short-form variants for X or LinkedIn
  • A comment and FAQ bank
  • A launch-day checklist

Output Style

  • Crisp, concrete, and human
  • Founder-written, not copywriter-written
  • Honest about tradeoffs, limitations, and current maturity

References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.