Landing page
Design and write high-converting single-offer landing pages: structure, copy, proof, FAQ, SEO/AEO. Use when building SaaS/app/service landings or rewriting heroes.From its SKILL.md
npx -y skills add swd3k/skills --skill landing-pageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 243 tokens by cl100k_base, as published. Nobody here has run it
Landing Page
One page · one audience · one primary action.
Gather first
- Primary CTA (trial / buy / waitlist / download)
- Offer, ICP, top objections
- Proof assets, risk reversal
- Traffic source
Structure
Above the fold: headline, subhead, CTA, proof, hero visual
Middle: problem→solution, benefits, how it works, social proof
Bottom: FAQ, risk reversal, final CTA
Layout picks
- Classic hero + sections (default)
- Long-form sales page (high skepticism)
- Minimal convert page (high intent)
- Comparison page (alternatives intent)
Copy rules
- Outcome + audience in headline
- Specificity beats "streamline"
- CTA = verb + value
- One primary CTA above the fold
Output
- Outline
- Hero copy
- Benefits (3–5)
- How it works (3)
- FAQ (6–12)
- SEO/AEO note
- Layout recommendation
Pitfalls
- Multiple competing CTAs
- Feature dump without outcomes
- Proof buried
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most design frontend skills give in 243 tokens
Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07
- Use CSS variables for color consistencyin 72 of 1169, across 23 files
- Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
- Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
- Add atmospheric background effects and texturesin 57 of 1169, across 9 files
- Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
- Implement real working codein 55 of 1169, across 7 files
- Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
- Launch chromium in headless modein 47 of 1169, across 4 files
- Close the browser when donein 47 of 1169, across 4 files
- Run provided scripts with help flag firstin 47 of 1169, across 4 files
- Wait for network idle statein 47 of 1169, across 4 files
- Use descriptive selectors for elementsin 47 of 1169, across 4 files
Said here and by no other author read
- gather primary CTA offer and proof assets first
- order middle sections from problem to social proof
- order bottom sections from FAQ to final CTA
- put outcome and audience in the headline
- make the CTA a verb plus value
- produce the specified seven-part output
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.