Individual skill

launch-post

Write a developer-audience launch post — Show HN, a Product Hunt blurb, a 'we shipped X' dev blog intro, or a launch tweet thread. Use when launching a tool, library, API, or open-source project to a technical audience. Produces a credible, hype-free post that leads with what it does and why it's different, plus title options and a comment-ready first reply.

plugins/pm-devrel/skills/launch-post/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Launch Post Skill

Developers smell marketing from a mile away. A launch post that lands with them is concrete, honest about
trade-offs, and leads with *what it does and why you built it* — not adjectives. This skill writes that post
(Show HN, Product Hunt, dev blog, or a tweet thread), tuned to the channel, with title options and a strong
first comment to seed the discussion.

## Required Inputs

Ask for these only if they aren't already provided:

- **What you built** — the tool/library/API, in one plain sentence.
- **The problem & why now** — what was painful before; why you made it.
- **What's different** — how it compares to the obvious alternatives (honestly).
Back to top