agentleFS
HayatelinHayatelin/founder-skills/skills/landing-page-copy/SKILL.md

landing-page-copy

Skill0 starsChanged 5 months agoMITView on GitHub

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".

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use direct-response-copy.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MoizIbnYousafSkill

    direct-response-copy

    Write copy that converts. Use when writing landing pages, emails, sales copy, headlines, CTAs, social posts, cold emails, or any persuasive text. Triggers on 'copy', 'copywriting', 'sales copy', 'landing page copy', 'cold email', 'headlines', 'write me a page', 'make this convert', 'rewrite this copy', or any request involving persuasive writing. Three modes: Generate (write from scratch), Edit (improve existing copy with Seven Sweeps), Cold Email (outbound sequences). If someone has text that needs to sell harder, this is the skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a founder needs landing-page copy that converts a cold visitor into a signup, demo request, or purchase — clear, specific, and …

    line 11
  2. Distinctive:

    If pre-launch, use a waitlist count or a credible founder-story line.

    line 27
  3. Distinctive:

    Avoid: feature dumps, jargon, hero that describes the company instead of the customer's win.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Product, ICP, and the #1 pain it kills.
  2. The single primary action you want visitors to take (signup / demo / buy / waitlist).
  3. Any proof: logos, metrics, testimonials, waitlist count.
  4. Pricing (if shown) and the top objections customers raise.

Process

  1. 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.
  2. Problem — 2-3 lines mirroring the pain in the ICP's own words so they feel seen.
  3. Features as benefits — for each top feature write "X so you can Y"; the benefit (Y) leads. 3-5 max.
  4. 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.
  5. Pricing — anchor to value; one tier highlighted; remove risk (free trial, no card).
  6. FAQ — answer the 4-5 objections that actually block the CTA (security, lock-in, "why not just use ChatGPT", migration effort).
  7. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.