SkillAgentSearch skills...

landing-page

Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.

Install / Use

npx skills add MengTo/Skills --skill landing-page

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Our assessment of landing-page

landing-page scores 85/100 on our quality scale, 781st of 1,153 Content & Media skills we index.

Its SKILL.md is 5.0 KB long, well organised into 34 sections and no code examples: a solid amount of guidance for an agent.

With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so landing-page is actively maintained.
  • Our last check on 2026-11-04 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

landing-page compared with similar skills

All 4 of these similar skills score higher than landing-page; compare them before choosing.

SkillScoreStarsUpdatedFormat
landing-page (this skill)by MengTo856.3k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md

Frequently asked questions

How do I install landing-page?
Run npx skills add MengTo/Skills --skill landing-page. The install tabs above show the steps for each supported agent.
Which AI agents does landing-page work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is landing-page safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is landing-page still maintained?
The repository was last updated about 2 months ago, so landing-page is actively maintained.

name: landing-page description: Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.

Landing Page (High‑Conversion) — Web Design Skill

A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent: one offer → one audience → one primary action.

Before you design/write

Gather (ask if missing):

1) Page purpose

  • What is the ONE primary action? (trial, demo, buy, waitlist, download)
  • What’s the offer? (exactly what do they get?)
  • What counts as conversion? (click, signup, purchase)

2) Audience + context

  • Who is the ICP?
  • What problem are they trying to solve?
  • Top 3 objections (why they don’t convert today)
  • Traffic source: ads / search / social / email
  • What do visitors already know when they land?

3) Proof + assets

  • Any proof points: logos, testimonials, numbers, case studies
  • Screenshots, demo video, product GIFs
  • Guarantees / refund / cancellation terms

4) Constraints

  • Brand voice: casual vs professional
  • Design direction: minimal editorial vs playful 3D vs glass UI
  • Mobile priority?

Core structure (what it should include)

Above the fold (must)

  1. Headline (outcome + audience)
  2. Subheadline (clarifies “how” + adds specificity)
  3. Primary CTA (clear verb + what they get)
  4. One proof signal (logo strip / stat / short testimonial)
  5. Hero visual (product screenshot/video) or a strong illustration

Mid page (argument)

  1. Problem → solution (1 section)
  2. Benefits (3–5, outcome-driven)
  3. How it works (3 steps)
  4. Social proof (testimonials/case study)

Bottom (objection handling)

  1. FAQ (6–12 Q/A)
  2. Risk reversal (trial, cancel anytime, guarantee)
  3. Final CTA (same as top)

Layout types (pick one)

A) Classic hero + sections (most common)

Best when:

  • product is understandable with a hero screenshot

B) Long-form story (sales page)

Best when:

  • you need to educate + overcome skepticism

C) Minimal conversion page

Best when:

  • high-intent traffic (email → known users)
  • short offer (download, waitlist)

D) Comparison landing page

Best when:

  • search intent includes alternatives (“X vs Y”, “best for…”)—usually paired with SEO pages

High‑conversion strategies (practical)

1) Match message to source

If traffic is from ads:

  • mirror the ad headline in the hero
  • use the same promise and visual tone

2) Make the next step obvious

  • one primary CTA
  • avoid multiple competing CTAs above the fold

3) Write benefit-first

  • Features: what it does
  • Benefits: what that means for them

4) Use specificity

  • ❌ “Save time and streamline”
  • ✅ “Cut your weekly reporting from 4 hours to 15 minutes”

5) Reduce risk

Pick at least one:

  • free trial
  • free plan
  • no credit card
  • cancel anytime
  • money-back guarantee

6) Objection handling is a section, not a footer

  • add FAQ earlier if it’s a high-friction offer
  • put proof right next to the claim it supports

Copywriting templates

Headline formulas

  • “{Outcome} without {pain}”
  • “The {category} for {audience}”
  • “Ship {result} in {time}”

Subheadline rules

  • 1–2 sentences
  • clarify what it is + who it’s for

CTA rules

  • Verb + what they get
  • Avoid weak CTAs: “Learn more”, “Submit”

Examples:

  • “Start free trial”
  • “Book a demo”
  • “Get the checklist”

Benefit bullets

Format:

  • Benefit — proof/detail

Example:

  • Faster iteration — generate 3 layout variants in one click.

Section-by-section workflow (designer-friendly)

Work in this order:

  1. Hero
  2. Benefits
  3. How it works
  4. Proof
  5. FAQ
  6. Final CTA

Rule: don’t rebuild the whole page each time. Iterate section-by-section to keep control.


SEO + AEO checklist (when relevant)

When landing pages should NOT be indexed

  • ad-only campaigns
  • highly time-bound offers

Use:

  • noindex (or keep it behind a non-indexed path)

When they SHOULD be indexed

  • evergreen offers
  • search intent matches the promise

Add:

  • clear title + meta
  • internal links from homepage/feature pages
  • FAQ in plain Q/A for AEO

Optional:

  • FAQ schema (if appropriate)

Common pitfalls

  • Too many CTAs above the fold
  • Vague value prop (“streamline”, “optimize”)
  • Big feature list with no outcomes
  • Proof hidden at the bottom
  • Mobile layout breaks readability
  • No clear next step

Output format (when generating a landing page)

Return:

  1. Page outline (sections + order)
  2. Hero copy (headline, subheadline, CTA, proof line)
  3. Benefits section (3–5 bullets)
  4. How it works (3 steps)
  5. FAQ (6–12 Q/A)
  6. SEO/AEO (indexing recommendation + title/meta if indexed)
  7. Layout recommendation (A/B/C/D + why)

Quick questions (if user says “make a landing page”)

  • What’s the ONE primary CTA?
  • Who is the ICP and what’s the main pain?
  • Any proof (numbers/testimonials/logos)?
  • What’s the offer and risk reversal?
  • Where is traffic coming from?

Related Skills

View on GitHub
GitHub Stars6.3k
CategoryContent
Updated1mo ago
Forks741

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions