Individual skill

landing-page-copy

Write landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping a new page for a launch or campaign. Do NOT use for testing and optimizing an existing page's conversion rate - use landing-page-cro instead; for the one-line claim itself use positioning-statement; for the full message ladder use messaging-hierarchy.

skills/landing-page-copy/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 24
Repository last updated: Oct 13, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude Repository topic
claude-skills Repository topic
skill-me Repository topic
marketing Derived category
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,050 bytes

Read excerpt


# Landing Page Copy

A landing page makes one promise and spends the rest of the page making it believable. The costly mistake this skill prevents is the clever-but-vague page: paid traffic arrives, reads "Supercharge your workflow," and bounces before learning what the product does. Clarity outsells cleverness, and the reader decides in the first five seconds whether to give you thirty more.

## Operating procedure

Write top to bottom in the order below, because each section answers the objection the previous one created: the hero makes a claim, proof makes it credible, benefits make it concrete, objections clear the residue, and the CTA collects.

### Step 1: Gather inputs

1. The one promise - the single outcome the page sells. If the user offers three, make them pick one; the others become body copy. If no positioning exists yet, route to positioning-statement first.
2. The ICP and the pain in their own words (support tickets, sales calls, reviews - not the founder's paraphrase). Label paraphrases as guesses.
3. The real alternative (spreadsheet, incumbent, doing nothing).
4. Available proof: testimonials, logos, numbers, screenshots. Default: if none exists, use specificity of mechanism as interim proof and flag the gap.