agentleFS
whawkinsivwhawkinsiv/claude-code-skills/skills/landing-page/SKILL.md

landing-page

Skill258 starsChanged 29 days agoMITView on GitHub

Use this skill to write or fix a page that sells: 'build my landing page,' 'homepage copy,' 'hero section,' 'sales page,' 'pre-sell page,' 'write a headline,' 'button text,' or 'people visit but don't sign up or buy.' Writes a page with one offer, one price, and one action (pay, pre-order, or book a call), using the customer's words and only real proof, then diagnoses where visitors drop off. Not for visual polish (use beautify) or for SEO pages (use seo).

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use operational-enterprise-ai, product-proof-saas and 9 more.

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.
  • boraoztuncSkill

    operational-enterprise-ai

    Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback. Use for dark cinematic heroes, hairline grids, metric pauses, expandable solution rows, case-study evidence, security proof, and qualified demo or waitlist handoffs.

    Also in 3 projects that use this

  • boraoztuncSkill

    product-proof-saas

    Create or redesign SaaS and AI product landing pages where a real workflow, interface, or deterministic demo is the central proof. Use for pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons, and FAQ handoffs.

    Also in 3 projects that use this

  • Dragoon0xSkill

    pricing-page

    Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.

    Also in 3 projects that use this

  • Dragoon0xSkill

    onboarding-flow

    Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.

    Also in 3 projects that use this

  • shawnpangSkill

    lead-scoring

    When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 4 projects that use this

  • +2 more from boraoztunc

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 2

    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:

    Read ABOUT-ME.md and any validation brief or customer notes in the project.

    line 14
  2. Distinctive:

    Specific beats vague: Use real numbers, and only real numbers.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 38 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

Landing Page

A landing page is a sales conversation, not a brochure. Early on, its job is to get a stranger to pay, pre-order, or book a call. A waitlist sign-up is only for a demand test in validate.

Step 1: Gather the material

Read ABOUT-ME.md and any validation brief or customer notes in the project. Then ask for what is missing:

  • the offer in one sentence: what the customer has before, and after
  • the price, or the price range
  • the one action: pay, pre-order, or book a call
  • the customer's own words for the problem: quotes from conversations, posts, or reviews
  • the real proof the founder has: paying customers, results, quotes given with permission, or the founder's own experience in the field

Step 2: Write the page in the order the buyer asks questions

  1. What is this? The hero: a headline that names the outcome, a subheadline that says how, one button, and the price or "from $X." Name the result: "Get paid in 7 days, not 45." Not "Smarter invoicing."
  2. Is it for me? The problem, in the customer's words. Name who it is for, specifically.
  3. How does it work? Three steps. If delivery is still by hand, describe what really happens after they pay: "I set it up for you within 48 hours."
  4. Can I trust you? The founder's story: the problem they ran into, and why they are the one to fix it. If the founder works in the customer's field, lead with that. "Built by a dentist who lost $2,000 a month to no-shows" beats any feature list. Add real proof, if any.
  5. What does it cost? One price, what is included, and the refund policy.
  6. Questions: answer the 4–6 objections the founder actually hears. Can I cancel? What happens to my data? How long does setup take?
  7. Final call to action: the same action, from a different angle.

Step 3: Copy rules

  • Outcome over feature. "Know exactly what's working" beats "Advanced analytics dashboard."
  • Specific beats vague. Use real numbers, and only real numbers.
  • The button names the action and its value. "Book a 15-minute setup call" or "Start for $49/month," not "Get started" or "Submit." Put a line under the button that answers the main worry: "Cancel anytime" or "Full refund within 14 days."
  • One page, one goal, one audience. Cut anything that serves another goal.
  • Write like the founder talks (ABOUT-ME.md), and run humanize on the final copy.

Step 4: Build it

Build the page in the project and apply beautify. It must be fast and readable on a phone. Most first visitors arrive from a link on their phone.

Step 5: Fix a page that does not convert

Find the step where visitors drop off: arriving, scrolling, clicking the button, or paying. For that step, check five things in order:

  1. Clarity: can a stranger tell what this is and what to do in 5 seconds?
  2. Motivation: is the value of acting now obvious?
  3. Friction: how many fields, clicks, or decisions stand in the way? Cut them.
  4. Anxiety: what fear stops them: price, commitment, data, or trust? Answer it next to the button.
  5. Distraction: what competes with the one action? Remove it.

Fix the biggest problem first. Change one thing at a time when traffic is low, so you can tell what worked.

Rules

  • Never invent proof. No placeholder testimonials, no made-up customer counts, no logos of companies that are not customers. Fake proof is a lie, and buyers can sense it. With no proof yet, use the founder's story, a guarantee, and a real way to talk to the founder.
  • Show the price. Hiding it slows down every buyer who is ready.
  • Do not lead with "free." A free plan attracts people who will not pay, and early on the founder needs to learn who will.

Output

The page copy, section by section, then the built page. For a review: the drop-off step, the five checks with findings, and the changes made.

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.