Landing page copy
A founder/indie-hacker skills pack for Claude Code, Cursor, Codex and Gemini CLI: market research, competitor analysis, outcome-based pricing, landing-page copy, MVP spec, cold outreach, growth experiments and fundraising narrative.
npx -y skills add Hayatelin/founder-skills --skill landing-page-copyAssembled 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
Writes a high-converting landing page — hero, subhead, problem, features-as- benefits, social proof, pricing, FAQ, and CTA. Trigger on "write my landing page", "homepage copy", "hero section", "make my copy convert", or "I need website copy for my startup".
SKILL.md
2.3 KB, as published. Nobody here has run it
When to use
When a founder needs landing-page copy that converts a cold visitor into a signup, demo request, or purchase — clear, specific, and benefit-led.
Inputs to gather
- Product, ICP, and the #1 pain it kills.
- The single primary action you want visitors to take (signup / demo / buy / waitlist).
- Any proof: logos, metrics, testimonials, waitlist count.
- Pricing (if shown) and the top objections customers raise.
Process
- Hero — outcome-led headline (the after-state, not the feature) + a subhead that names the ICP and the mechanism in one line. Lead with clarity over cleverness.
- Problem — 2-3 lines mirroring the pain in the ICP's own words so they feel seen.
- Features as benefits — for each top feature write "X so you can Y"; the benefit (Y) leads. 3-5 max.
- Social proof — logos, a metric ("cut resolution time 40%"), or a punchy quote. If pre-launch, use a waitlist count or a credible founder-story line.
- Pricing — anchor to value; one tier highlighted; remove risk (free trial, no card).
- FAQ — answer the 4-5 objections that actually block the CTA (security, lock-in, "why not just use ChatGPT", migration effort).
- CTA — one primary action, repeated 2-3x, written as a benefit ("Start resolving tickets free"), never "Submit".
Output
A ready-to-paste page in sections, each labeled:
[HERO] headline + subhead + CTA · [PROBLEM] · [BENEFITS] (3-5 blocks) ·
[SOCIAL PROOF] · [PRICING] · [FAQ] (4-5 Q&A) · [FINAL CTA].
Include 2 headline variants for A/B testing.
Quality bar & pitfalls
- Good = a stranger gets "what it is, who it's for, why I'd act" in under 5 seconds.
- One page, one primary CTA. Specificity beats adjectives ("40% fewer tickets" > "revolutionary").
- Address the "why not just use ChatGPT/Claude?" objection head-on — point at your moat.
- Avoid: feature dumps, jargon, hero that describes the company instead of the customer's win.