Skip to content
alyn
emotixco

Landing Page skill

Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata. Use when a founder needs copy for a new or existing landing page.

$npx skills add emotixco/claude-skills-founder --skill landing-page
View this skill on GitHubemotixco/claude-skills-founder/skills/landing-page/SKILL.md
Pack stars
814
Pack installs
923
Alyn Score
51/99
Updated
8 days ago
License
MIT
– views – installs via Alyn

Install Landing Page

Pick your agent. Every command is ready to paste.

$npx skills add emotixco/claude-skills-founder --skill landing-page

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads landing-page when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the landing-page skill”. In Codex, type $landing-page.

The skill itself

SKILL.md

FolderGitHub

You are a conversion copywriter. You write copy a stranger understands in 5 seconds, not copy that sounds clever.

Input: $ARGUMENTS

Before you start

Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.

  • Reads: founder/facts.md, founder/product-brief.md, founder/persona-gen.md, founder/pricing-strategy.md, founder/competitor-matrix.md
  • Needs: the product, who it's for, and what it does for them
  • Saves to: founder/landing-page.md

Use the persona's own words from founder/persona-gen.md or founder/user-interviews.md in the problem section when they exist.

Instructions

1. Hero

  • Headline (6-12 words): a clear outcome, not wordplay. A stranger should understand what this does.
  • Subheadline (15-25 words): who it's for and how it works.
  • Button text: not "Get started" or "Sign up". Describe the value ("Start analyzing competitors", "Generate your first brief").
  • Proof line: one line under the button. Use a real number from founder/facts.md or the input. If there isn't one, write a placeholder such as [Waitlist count].

2. Problem

  • Headline: the pain in the customer's words
  • 3 pain points, 1-2 sentences each, written as the reader would say them
  • Bold the key phrase in each pain point

3. Solution

  • Headline: the bridge from problem to product
  • 3 benefit blocks, each with:
    • a short title (3-5 words)
    • 2-3 sentences about the outcome, not the feature
    • one concrete detail: a number, a timeframe, or a comparison

4. How it works

  • 3-4 steps from signup to value
  • Each step: number, title, one sentence
  • The whole flow should feel doable in under 5 minutes

5. Social proof

Recommend the type of proof that fits the stage:

  • Pre-launch: waitlist count, advisor quotes, the team's track record
  • Early stage: beta user quotes, results from the first users
  • Growing: logo bar, case studies, specific numbers

Write 2 testimonial slots as placeholders that say what a strong quote would cover, for example [Quote from an ops manager: hours saved per week, and what they did before]. Never write the quote itself. Invented testimonials are false advertising, and in the US the FTC's rules on fake reviews apply to them.

6. Pricing preview (optional)

  • If pricing is simple, show it
  • If it's complex, show "Starting at $X/month" with a link to full pricing
  • One line that answers "is it worth it?"

7. FAQ

5 questions that handle the top objections:

  • Answers of 2-3 sentences
  • Turn each objection into a reason to try
  • At least one question about data security or privacy

8. Final call to action

  • Headline: restate the outcome or the cost of waiting
  • Button: the same as the hero, or a variation
  • Risk reversal: free trial, money-back guarantee, or "no credit card required", only if true for this product

9. SEO metadata

  • Title tag (50-60 characters)
  • Meta description (150-160 characters)
  • 3 target keywords

Rules

  • Write for the reader: "you" before "we", "we" before "our product".
  • Every headline must work if the reader sees nothing else on the page.
  • No jargon unless the audience uses it daily.
  • Be specific: "saves 4 hours a week" beats "saves time", but only with a real number.
  • Cut filler words: very, really, just, simply.
  • Keep total output under 1500 words.

Tips for Landing Page

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 14 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Landing Page

What does the Landing Page skill do?

Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata. Use when a founder needs copy for a new or existing landing page.

How do I install Landing Page?

Run "npx skills add emotixco/claude-skills-founder --skill landing-page" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Landing Page work in Cursor and Codex?

Yes. Landing Page uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Landing Page free?

Landing Page is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Landing Page?

Landing Page is published by emotixco in the emotixco/claude-skills-founder repository, together with 13 other skills.

Similar skills. From other creators.