landing-page · emotixco — Claude Code skill: copy and installation
This Claude Code skill drafts landing page copy from the hero section through the final call to action. It runs when creating a page for a new or existing product.
MIT ★ 900 updated 2026-11-03
npx skills add emotixco/claude-skills-founder --skill landing-page -a claude-codeWhat landing-page does
The skill builds landing page copy one section at a time and adds SEO metadata. Its output covers the customer problem, the product solution, steps for getting value, social proof, a pricing preview, FAQs and a closing call to action.
It reads product facts, briefs, personas, pricing strategy and competitor research from founder/. The result goes to founder/landing-page.md, and the skill reads ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md before starting. It needs information about the product, its audience and the value it offers.
Testimonial areas are placeholders, not fabricated quotes. If the product facts contain no real number for the line below the hero button, the skill leaves a placeholder such as [Waitlist count].
What it helps with
- draft page copy from the hero through the final call to action
- turn product benefits into separate landing page sections
- write objection-handling FAQs and SEO metadata
- leave testimonial slots without inventing quotes
Example prompts for the agent
- Write landing page copy for our product, its audience, and its main value.
- Create a product page from the materials in
founder/and save it tofounder/landing-page.md. - Draft a landing page with benefit sections, FAQs, and SEO metadata.
How to install landing-page
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill landing-page -a claude-code2Manually: put the files in place
~/.claude/skills/landing-page/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/landing-page/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill landing-page -a codex2Manually: put the files in place
.agents/skills/landing-page/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill landing-page -a cursor2Manually: put the files in place
.cursor/skills/landing-page/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install emotixco/claude-skills-founder skills/landing-page2Manually: put the files in place
.github/skills/landing-page/SKILL.md1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill landing-page -a gemini-cli2Platform CLI
gemini skills install https://github.com/emotixco/claude-skills-founder --path skills/landing-pageManually: put the files in place
.devin/skills/landing-page/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill landing-page -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about landing-page
How do I install landing-page in Claude Code?
Run npx skills add emotixco/claude-skills-founder --skill landing-page -a claude-code. The skill file is at ~/.claude/skills/landing-page/SKILL.md.
What does landing-page do?
It drafts landing page copy in sections, including the hero, problem, solution, FAQ, final call to action and SEO metadata. It saves the page to founder/landing-page.md.
What does landing-page need to work?
It needs information about the product, its audience and the value it provides. The skill also reads ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and materials from founder/.
Source text
SKILL.md · MIT
---
name: landing-page
description: 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.
argument-hint: "[your product, target audience, and main value]"
allowed-tools: Read Edit(founder/**)
---
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.
© emotixco · MIT · emotixco/claude-skills-founder
Similar skills
All skills for Marketing and content →landing-page by other authors comes first.