Skip to content
cccskills
FreePublished on GitHub

landing-page

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.

The English summary is being prepared. Showing the original description.

emotixco/claude-skills-founder732 stars(GitHub 732 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Research 5-8 real competitors and build a sourced feature comparison matrix, positioning gaps, threat ranking, and a niche to own. Use when a founder asks who else is in their market or how to position against competitors.

The English summary is being prepared. Showing the original description.

emotixco/claude-skills-founder732Updated Oct 21, 2026

Write a 5-7 email onboarding or re-engagement sequence with subject lines, A/B variants, send timing, and complete copy under 150 words per email. Use when a founder needs lifecycle emails for a product.

The English summary is being prepared. Showing the original description.

emotixco/claude-skills-founder732Updated Oct 21, 2026

Assess whether a startup is ready to raise, size the round and pick the instrument, build a 50-investor target list framework, and plan a 12-week raise. Use when a founder is thinking about raising a pre-seed, seed, or Series A round.

The English summary is being prepared. Showing the original description.

emotixco/claude-skills-founder732Updated Oct 21, 2026

Plan a product launch from pre-launch audience building to a 90-day growth plan, with named communities, platform-specific launch tactics, channel rankings, and a budget for $0-$500 a month. Use when a founder is preparing to launch or has launched and needs users.

The English summary is being prepared. Showing the original description.

emotixco/claude-skills-founder732Updated Oct 21, 2026

Pick the 5 metrics that matter at a startup's current stage, with definitions, targets, actions when below target, a minimal tracking setup, and a weekly review template. Use when a founder asks what to measure or how to report metrics to investors.

The English summary is being prepared. Showing the original description.

emotixco/claude-skills-founder732Updated Oct 21, 2026

Cut a feature wishlist down to the smallest MVP that delivers value. Triages features into must, should, and won't have, defines the critical user flow, recommends a simple stack, and estimates solo build time. Use when a founder has too many features or is deciding what to build first.

The English summary is being prepared. Showing the original description.

emotixco/claude-skills-founder732Updated Oct 21, 2026

See all skills by emotixco

Report a problem with this skill