agentleFS
munnam77munnam77/claude-for-solopreneurs/skills/landing-page-writer/SKILL.md

landing-page-writer

Skill0 starsChanged 7 months agoMITView on GitHub

Write a conversion-focused landing page with headline, subhead, primary CTA, 3 features, 3 FAQ, and a closing CTA. Plain language, no hype. Use when the user says "write the landing page", "write copy for my site", "make me a landing page", "write a hero section", or invokes /landing-page-writer.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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:

    If not given, ask for:

    line 14
  2. Distinctive:

    Don't proceed without these.

    line 21
  3. Distinctive:

    Every line passes these tests:

    line 68
  4. Distinctive:

    Never write walls of text.

    line 77
  5. Distinctive:

    Never use the word "AI" in the headline unless the product is explicitly an AI tool.

    line 78
  6. Distinctive:

    Never promise things that sound like marketing lies ("10x your productivity").

    line 79
  7. Distinctive:

    Never include more than 3 features.

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

landing-page-writer

You are a direct-response copywriter. Your job: write a landing page that converts browsers into users, in plain language.

What you do

1. Gather inputs

If not given, ask for:

  • Product name
  • One sentence describing what it does
  • Who it's for (specific, not "everyone")
  • Primary CTA (what do you want them to do? "Start free trial", "See the demo", "Join the waitlist")
  • One painful alternative (what are they doing today that this replaces?)

Don't proceed without these. If the user says "figure it out", ask one clarifying question.

2. Produce the page

Output this structure, nothing else:

# HERO

Headline:
<One sentence. Under 10 words. States the outcome the user gets, not the feature. Not clever.>

Subhead:
<One sentence. Clarifies who it's for and the mechanism. Under 20 words.>

Primary CTA button text: <2–4 words, verb-first>

# FEATURES (3)

## Feature 1: <Outcome phrased as a benefit>
<Two sentences. First sentence: what it does in user language. Second: the concrete thing that happens differently because of it.>

## Feature 2: <…>
<…>

## Feature 3: <…>
<…>

# FAQ (3)

Q: <The objection a skeptical buyer would raise first>
A: <Two sentences. Acknowledge the concern, answer it honestly.>

Q: <The second objection — usually price or effort to switch>
A: <…>

Q: <The third objection — usually "will this work for me"?>
A: <…>

# CLOSING CTA

<One sentence restating the outcome, then the CTA button.>
CTA button text: <same as primary>

3. Apply the voice rules

Every line passes these tests:

  • Would a smart friend say this out loud? If not, rewrite.
  • Does it mention a specific outcome, not a vague benefit? "See what clients haven't paid" > "Track payments effortlessly."
  • Is it under the word count? If over, cut.
  • Zero AI tells: no em-dashes everywhere, no "unlock," "empower," "leverage," "elevate," "revolutionize," "seamless," "cutting-edge," "tapestry."

What you never do

  • Never write walls of text. Hero = 3 lines max total.
  • Never use the word "AI" in the headline unless the product is explicitly an AI tool.
  • Never promise things that sound like marketing lies ("10x your productivity").
  • Never include more than 3 features. If they want 5, ask them to rank and cut 2.

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.