Landing Page Generator

VerifiedSafe

Generate complete, high-converting landing pages from a product or service brief. Use when building landing pages, sales pages, or marketing pages for clients. Outputs production-ready HTML/CSS that is mobile-responsive and optimized for conversions.

Sby Skills Guide Bot
ContentBeginner
3/8/2026
Claude Code
#landing-pages#html-css#marketing#conversion-optimization#responsive-design

Recommended for

Automated summary

Generates a self-contained, mobile-responsive HTML/CSS landing page from a product or service brief, structured for conversion.

Strengths

  • Picks a page template automatically (SaaS, service, portfolio, lead magnet, e-commerce, event) based on the brief
  • Outputs one HTML file with embedded CSS and no external dependencies besides Google Fonts
  • Covers the core conversion sections: hero, benefits, social proof, pricing, FAQ, final CTA
  • Ships a coherent design system (Inter typography, CSS variable color palette, responsive grid)

Limitations

  • Visuals stay as placeholders: Unicode/emoji icons and logo boxes, no real imagery
  • No advanced SEO, analytics, or conversion tracking is described
  • Copy quality depends heavily on how much detail the brief provides
When to use it

Use it when you need to deliver a complete, responsive marketing page to a client quickly from a written brief.

When not to use it

Avoid it if you need a multi-page site wired into a framework, or a page with real visual assets and tracking already integrated.

Security analysis

Safe
Quality score86/100

This is a purely generative design skill: it reads a brief, produces a self-contained HTML file and README, and applies standard web-design/accessibility principles. There is no curl|sh, no credential or token handling, no deletion of user data, and no instruction to disable safety checks. The inclusion of Bash and Write/Edit tools is a mild capability escalation but is bounded to writing an output directory, so the listing presents no meaningful execution risk.

Findings
  • •Bash is declared in allowed-tools but no destructive, network-exfiltrating, or obfuscated commands are described; usage appears limited to creating output directories
  • •Skill writes files only under output/landing-page/ — scoped and non-destructive
How this analysis is made

Examples

SaaS landing page
/landing-page-generator "SaaS project management tool for remote teams, $29/mo, free trial"
Portfolio with call booking
/landing-page-generator "Freelance web developer portfolio — book a call CTA"
From a brief file
/landing-page-generator brief.txt

name: landing-page-generator description: Generate high-converting, mobile-responsive landing pages from a brief. Use when building landing pages, sales pages, or marketing pages for clients. argument-hint: "[product-or-service-description]" allowed-tools: Read, Write, Edit, Grep, Glob, Bash

Landing Page Generator

Generate complete, high-converting landing pages from a product/service brief. Outputs production-ready HTML/CSS that's mobile-responsive and optimized for conversions.

How to Use

/landing-page-generator "SaaS project management tool for remote teams, $29/mo, free trial"
/landing-page-generator brief.txt
/landing-page-generator "Freelance web developer portfolio — book a call CTA"

Provide as much context as possible:

  • What the product/service is
  • Target audience
  • Primary CTA (sign up, buy, book a call, download)
  • Pricing (if applicable)
  • Key features/benefits
  • Brand colors (optional, defaults to professional blue/dark theme)

Page Generation Process

Step 1: Analyze the Brief

Extract:

  • Product type: SaaS, physical product, service, portfolio, lead magnet, event
  • Target audience: Who is this for?
  • Primary CTA: What action should visitors take?
  • Value proposition: Why should they care?
  • Tone: Professional, casual, bold, minimal, luxurious

Step 2: Select Page Template

Based on product type:

| Type | Sections | Typical Length | |------|----------|---------------| | SaaS | Hero, Features, How It Works, Pricing, Testimonials, FAQ, CTA | Long | | Service | Hero, Services, Process, Portfolio, Testimonials, CTA | Medium | | Portfolio | Hero, Work Samples, About, Services, Contact | Medium | | Lead Magnet | Hero, Benefits, Social Proof, Form, CTA | Short | | E-commerce | Hero, Product Features, Gallery, Reviews, Buy CTA | Medium | | Event | Hero, Speakers/Details, Schedule, Tickets, FAQ | Medium |

Step 3: Generate the Page

Create a single self-contained HTML file with embedded CSS. No external dependencies except Google Fonts.

Required sections (adapt to product type):

Hero Section

- Headline: Clear value proposition (max 10 words)
- Subheadline: Supporting detail (max 25 words)
- CTA button: High-contrast, action-oriented text ("Start Free Trial", not "Submit")
- Optional: Hero image placeholder or background
- Optional: Social proof badge ("Trusted by 10,000+ teams")

Features/Benefits

- 3-4 feature cards with icons (use Unicode/emoji icons)
- Each card: Icon + Feature name + 1-2 sentence benefit (focus on outcome, not feature)
- Grid layout: 3 columns on desktop, 1 on mobile

Social Proof

- 2-3 testimonial cards with:
  - Quote text
  - Name and title/company
  - Star rating (if applicable)
- Optional: Logo bar of client/partner logos (placeholder boxes with company names)

How It Works (if applicable)

- 3-step process with numbered steps
- Step title + brief description
- Visual connector between steps

Pricing (if applicable)

- 1-3 pricing tiers in card format
- Highlight the recommended tier
- Feature comparison list
- CTA button on each tier

FAQ

- 4-6 common questions
- Accordion-style (click to expand) using pure CSS/HTML <details>

Final CTA

- Repeat the primary CTA with urgency
- Different angle from hero (address remaining objections)
- Strong contrasting background

Step 4: Design System

Apply these design principles:

Typography:

  • Font: Inter from Google Fonts (clean, modern, high readability)
  • Heading scale: 3rem, 2rem, 1.5rem, 1.25rem
  • Body: 1rem / 1.6 line-height
  • Max line width: 65ch for readability

Colors (default, override with brand colors if provided):

--primary: #2563eb;        /* Blue - CTAs, links */
--primary-dark: #1d4ed8;   /* Hover state */
--bg: #ffffff;             /* Background */
--bg-alt: #f8fafc;         /* Alternating section bg */
--text: #1e293b;           /* Body text */
--text-light: #64748b;     /* Secondary text */
--accent: #f59e0b;         /* Highlights, badges */

Layout:

  • Max width: 1200px, centered
  • Section padding: 80px vertical (48px on mobile)
  • Consistent spacing scale: 4, 8, 16, 24, 32, 48, 64, 80px

Responsive breakpoints:

  • Desktop: 1024px+
  • Tablet: 768px - 1023px
  • Mobile: < 768px

Step 5: Conversion Optimization

Apply these conversion principles to the generated page:

  1. Above the fold: Headline + CTA visible without scrolling
  2. Single CTA focus: One primary action, repeated 2-3 times throughout
  3. Contrast ratio: CTA buttons must have WCAG AA contrast (4.5:1 minimum)
  4. Loading speed: No external JS, minimal CSS, no images (placeholders only)
  5. Scannability: Users should understand the offer in 5 seconds
  6. Objection handling: FAQ and testimonials address common concerns
  7. Urgency/scarcity: Optional — only if authentic ("Limited beta spots", not fake countdowns)

Step 6: Output

Save to output/landing-page/:

output/landing-page/
  index.html          # Complete self-contained page
  README.md           # Customization guide for the client

README.md includes:

  • How to customize colors (CSS variables at top of file)
  • How to replace placeholder content
  • How to add real images
  • How to connect forms to their email service
  • How to deploy (Netlify drag-and-drop, GitHub Pages, any static host)

Step 7: Present to User

Show:

  1. Brief summary of what was generated
  2. Key design decisions made
  3. File location
  4. Suggestions for what the client should customize (images, testimonials, specific copy)

Quality Standards

  • [ ] Page loads with no external dependencies except Google Fonts
  • [ ] Fully responsive at 320px, 768px, and 1200px widths
  • [ ] All CTA buttons have hover states
  • [ ] Color contrast meets WCAG AA
  • [ ] Page has proper <meta> viewport tag
  • [ ] Semantic HTML (<header>, <main>, <section>, <footer>)
  • [ ] No horizontal scroll at any breakpoint
  • [ ] FAQ sections are interactive (expand/collapse)
  • [ ] Total HTML file size under 50KB

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/landing-page-generator-mmh8qqlz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/landing-page-generator-mmh8qqlz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/landing-page-generator-mmh8qqlz/download' --output '.skill-downloads/landing-page-generator-mmh8qqlz/SKILL.md.part' && mv '.skill-downloads/landing-page-generator-mmh8qqlz/SKILL.md.part' '.skill-downloads/landing-page-generator-mmh8qqlz/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Grep, Glob, Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/landing-page-generator-mmh8qqlz/SKILL.md' && test -s '.skill-downloads/landing-page-generator-mmh8qqlz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/landing-page-generator' && cp -R '.skill-downloads/landing-page-generator-mmh8qqlz' '.claude/skills/landing-page-generator'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/landing-page-generator-mmh8qqlz'

openskills read 'landing-page-generator-mmh8qqlz'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/landing-page-generator-mmh8qqlz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills