agentleFS
buildfastwithaibuildfastwithai/gen-ai-experiments/skills/landing-page-generator/SKILL.md

landing-page-generator

Skill790 starsChanged 4 months agoMITView on GitHub

Generate high-converting landing pages as production-ready HTML with built-in design themes, copy frameworks (PAS, AIDA, BAB), CTA strategy, SEO meta, and automated conversion/speed audits. Use whenever the user wants a landing page, campaign page, lead capture page, promo page, launch page, or single-page site — or wants an existing landing page reviewed, audited, or improved — even if they don't say "landing page" (e.g. "a page for my product", "somewhere to send ad traffic", "a signup page for the webinar").

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paid-ads, page-cro and 1 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.
  • silvainfmSkill

    paid-ads

    When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.

    Also in 3 projects that use this

  • silvainfmSkill

    page-cro

    When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

    Also in 3 projects that use this

  • ukunal91appSkill

    cold-email

    Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run all three against the finished HTML (they support --json for machine-readable output):

    line 73
  2. Very specific:

    If the page will receive real traffic, suggest an A/B test on the headline — commonly the highest-impact element (framework in …

    line 87
  3. Very specific:

    When asked to review/improve an existing landing page rather than build one: run all three scripts on it, read references/optimization.md …

    line 91

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

Build landing pages that convert, as a single self-contained HTML file, then verify them with the bundled audit scripts.

Bundled Resources

ResourceWhat It's ForWhen to Read/Run
assets/template.htmlProduction-ready page scaffold: 9 sections, 4 themes, SEO meta, schema, CWV optimizations baked inCopy as the starting point for every new page
references/copy-frameworks.mdPAS/AIDA/BAB application, hero copy rules, CTA formulas, voice rulesBefore writing any copy
references/section-library.mdSection-by-section patterns, variants, and rulesWhen adding/removing/adapting sections
references/design-styles.mdTheme selection, tokens, typography, imagery rulesWhen choosing a theme or applying brand colors
references/optimization.mdManual checklists, CWV targets, A/B testing, troubleshooting, benchmarksBefore delivery; when diagnosing an underperforming page
scripts/*.pyAutomated audits (see Verify step)After every draft, before delivery

Clarify First

Confirm these before generating. Ask only the 2-3 that most change the output; if the user says "just draft it," proceed and list assumptions at the top of the deliverable.

  • Conversion goal & offer — the single action and what the visitor gets (one page, one goal, one CTA)
  • Target audience & awareness level — selects the copy framework (see below)
  • Key pain point & key benefit — drives the hero headline and Problem/Solution sections
  • Traffic source — ads, email, or organic (sets message match)
  • Brand constraints — existing colors/logo/screenshots, or free rein

Workflow

1. Choose framework and theme

Copy framework by audience awareness (details in references/copy-frameworks.md):

AudienceFramework
Knows the problemPAS
Needs educationAIDA
Wants transformation, knows solutions existBAB

Design theme by product type (details in references/design-styles.md): dark-saas (dev tools, technical SaaS), clean-minimal (services, healthcare, education), bold-startup (consumer, creative), enterprise (B2B enterprise, finance, government).

2. Build from the template

Copy assets/template.html, set data-theme on <body>, and replace every {{PLACEHOLDER}}. The template's section order is canonical: Hero → Social proof bar → Problem → Solution → How it works → Testimonials → Pricing → FAQ → Final CTA. Remove sections that don't apply (e.g., Pricing on a lead-magnet page) but don't reorder — credibility must precede claims, and objection-handling must precede the final ask.

Non-negotiables the template already enforces — keep them intact when editing:

  • One H1; nav is logo + CTA only (every extra link is an exit path)
  • Same CTA action repeated ~3 times, friction reducer under each button
  • Explicit width/height on images, loading="lazy" below the fold, fetchpriority="high" on the hero image
  • Viewport meta, meta description, OG tags, FAQPage schema

Honesty rule: never invent testimonials, customer names, logos, metrics, or guarantees. If the user hasn't supplied them, leave clearly marked placeholders and list what's needed. Fabricated social proof is a legal and trust liability for the user.

3. Verify with the audit scripts

Run all three against the finished HTML (they support --json for machine-readable output):

python scripts/conversion_checklist.py page.html   # 20+ point structure audit
python scripts/cta_analyzer.py page.html           # CTA placement, copy strength, consistency
python scripts/page_speed_estimator.py page.html   # Est. Core Web Vitals (LCP, CLS, INP)

Fix anything below grade B and every flagged issue, then re-run. Also do the manual checks in references/optimization.md (the scripts can't judge whether the headline actually communicates value — read it cold).

4. Deliver

Provide the HTML file plus a short summary: framework and theme chosen (and why), audit scores, assumptions made, and the placeholders the user still needs to fill (images, real testimonials, signup URL, analytics).

If the page will receive real traffic, suggest an A/B test on the headline — commonly the highest-impact element (framework in references/optimization.md).

Auditing an Existing Page

When asked to review/improve an existing landing page rather than build one: run all three scripts on it, read references/optimization.md for the manual checks and troubleshooting table, and present findings ordered by conversion impact (message match and above-fold CTA issues first, cosmetics last).

Scope

In scope: page structure, copy application, design themes, conversion optimization, CTA strategy, SEO meta, CWV optimization, A/B test design, auditing existing pages.

Out of scope: running the ad campaigns that drive traffic, CMS/website-builder administration, analytics platform setup, backend form processing (the template's form points to a URL the user must wire up).

Benchmarks caveat: conversion medians (~6.6% across industries, 2025) vary hugely by category — SaaS trials 10-25%, e-commerce 2-3%. Treat as directional; the user's own baseline is the real benchmark.

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.