agentsclimarketplace

Launch that converts

Skill lexthirteen-ai/founder-survival-kit/skills/launch-that-converts

Claude skills for the hard parts of building, now that ai made the building easy

Install
npx -y skills add lexthirteen-ai/founder-survival-kit --skill launch-that-converts

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

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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

Plans the month before a launch, because that is what decides launch day. Helps a founder pick the one outcome a launch should produce, build the audience and proof in the weeks before, prepare the assets and supporters, and run the day itself, so a launch is a payoff rather than a hail mary. Use when someone is planning a launch (Product Hunt, app store, Show HN, a public release), thinks launches "do not work," or is deciding whether a big launch is even the right move. Plans the run-up, it does not promise virality.

SKILL.md

3.3 KB, as published. Nobody here has run it

Launch That Converts

Founders call launches a waste of time when the launch was the whole plan. The useful read is not that launches are dead, it is that a launch only converts if you spent the weeks before it building the audience that shows up on the day. This skill plans that run-up.

When to use

  • You are planning a launch on any channel and want it to matter.
  • A past launch felt like shouting into a void.
  • You are not sure a big launch is even the right move for what you have.

Process

  1. Pick the one outcome. Decide the single thing this launch is for: sign-ups, revenue, feedback, credibility, or awareness. A launch aimed at everything converts on nothing. Everything below serves this one outcome.
  2. Sanity-check whether to launch at all. A launch amplifies what you already have. If there is no audience and no proof yet, the honest move may be to spend the next month on first-ten-users and build-in-public-engine and launch later. Say so if that is the case.
  3. Build the run-up (the real work). In the weeks before, grow the audience that will show up: build in public, collect the proof and testimonials, line up the specific people who will support on the day, and warm up the channel you are launching on by being present in it first.
  4. Prepare the assets. The page, the demo, the clear one-line description, the visuals, the first comment, the answers to the obvious questions. Ready days early, not the night before.
  5. Run the day. Ship early in the day, tell the supporters you lined up, be present to answer every comment quickly, and point your owned channels (list, community) at it. Momentum in the first hours is mostly the run-up paying off.
  6. Harvest afterward. Follow up with everyone who engaged, turn the attention into owned distribution (capture emails), and write down what actually drove the outcome for next time.

Output

  • The one launch outcome, named.
  • An honest go or wait call, with reasoning.
  • A week-by-week run-up plan for the weeks before launch.
  • A launch-day checklist and an asset list.
  • A post-launch follow-up plan that turns attention into owned distribution.

Guardrails

  • The run-up is the launch. Most of the effort belongs before the day. Do not let asset polish crowd out audience building.
  • One outcome. Refuse the temptation to aim a single launch at every goal.
  • Honest go or wait. If launching now would waste the one shot, say wait and explain why.
  • No manufactured hype. No bought upvotes, fake urgency, or engagement rings. Borrowed momentum does not convert and it costs trust.

Related

Depends on first-ten-users and build-in-public-engine for the run-up, and on ship-it-for-real and prelaunch-security-pass so the launch does not amplify something broken.

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.