landing-page
Use this skill when the user needs to create or improve a landing page, write above-the-fold copy, structure a sales page, or increase landing page conversion rates. Also use when the user says 'build my landing page,' 'homepage copy,' 'hero section,' or 'marketing site.' Covers page structure, headline formulas, buyer psychology, and conversion elements.
Best use case
landing-page is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when the user needs to create or improve a landing page, write above-the-fold copy, structure a sales page, or increase landing page conversion rates. Also use when the user says 'build my landing page,' 'homepage copy,' 'hero section,' or 'marketing site.' Covers page structure, headline formulas, buyer psychology, and conversion elements.
Teams using landing-page should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/landing-page/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How landing-page Compares
| Feature / Agent | landing-page | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when the user needs to create or improve a landing page, write above-the-fold copy, structure a sales page, or increase landing page conversion rates. Also use when the user says 'build my landing page,' 'homepage copy,' 'hero section,' or 'marketing site.' Covers page structure, headline formulas, buyer psychology, and conversion elements.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# Landing Page A landing page is a sales conversation, not a brochure. You have 5 seconds to communicate what the product does and why it matters. This skill gives you the structure and copy for every section. ## Core Principles - A landing page has ONE goal. Everything serves that goal or gets cut. - Structure follows the buyer's internal monologue: "What is this?" -> "Is it for me?" -> "How does it work?" -> "Can I trust it?" -> "What do I do next?" - Above the fold is the most valuable real estate on the internet. - Long pages can outperform short pages — IF every section earns its place. --- ## Workflow ``` Landing Page Build: - [ ] Define the ONE goal (signup, waitlist, demo request) - [ ] Write the hero section (headline + subheadline + CTA) - [ ] Plan sections in scroll order - [ ] Write copy for each section - [ ] Build the page - [ ] Test on mobile - [ ] Add analytics tracking (see analytics skill) ``` --- ## Section-by-Section Build ### Hero (Above the Fold) The hero has 5 elements. Get these right and the rest is easier. 1. **Headline** — State the outcome, not the product. - Be specific: "Cut your deploy time from 45 minutes to 45 seconds" - Not: "Deploy faster" 2. **Subheadline** — Add the "how" or a second benefit. 3. **Primary CTA** — High contrast, specific action text. "Start building free" not "Get started." 4. **Visual** — Product screenshot, short demo, or animated illustration. Show the product in action. 5. **Social proof bar** — Logo strip or metric: "Trusted by 15,000+ teams" **Tell AI:** ``` Write the hero section for our landing page: - Product: [what it does, one sentence] - Audience: [who it's for] - Main benefit: [the #1 outcome users get] - Social proof: [number of users, notable customers, or key metric] Give me: - 3 headline options (under 10 words each, outcome-focused) - Subheadline for each (adds "how" or second benefit) - Primary CTA button text + anxiety reducer below it - Social proof line Pick the strongest option and explain why. ``` ### How It Works Exactly 3 steps. Cognitive simplicity. Format: [Number/Icon] + [Short title] + [One sentence] Example: 1. **Connect your repo** — Link your GitHub in one click. 2. **Configure your pipeline** — Our AI suggests the optimal setup. 3. **Ship with confidence** — Deploy automatically on every push. ### Feature Sections Alternate layout: text-left/image-right, then text-right/image-left. Each feature: [Eyebrow label] + [Benefit headline] + [2-3 sentence description] + [Screenshot] Lead with benefit, not feature name: - BAD: "Advanced Analytics Dashboard" - GOOD: "Know exactly what's working — and what's not" ### Testimonials - Include: Name, title, company, headshot. - Quote should mention: a specific result, a before/after, or an emotional reaction. - GOOD: "We cut onboarding from 2 weeks to 2 days. New hires actually thank us now." — Sarah Chen, VP Eng @ Acme - BAD: "Great product, really love it!" — J.S. - Place near objection points (security testimonial near pricing, etc.) ### FAQ Must answer for any SaaS: 1. "Is there a free plan / trial?" 2. "How long does setup take?" 3. "Can I cancel anytime?" 4. "Is my data secure?" 5. "What integrations do you support?" 6. One or two product-specific questions. ### Final CTA Repeat the primary CTA with a slightly different angle. Different headline, same action. --- ## Full Page Build **Tell AI:** ``` Build a landing page for our SaaS product: - Product: [what it does] - Audience: [who it's for] - Main benefit: [#1 outcome] - Features: [list 3-4 key features] - Social proof: [logos, metrics, testimonials you have] - CTA: [what you want visitors to do — signup, waitlist, demo] Use this section order: 1. Hero (headline, subheadline, CTA, social proof bar) 2. Problem agitation (articulate the pain they're feeling) 3. How it works (3 steps) 4. Feature sections (3-4, alternating layout with screenshots) 5. Testimonials (use placeholders if I don't have real ones yet) 6. Pricing preview or "See plans" CTA 7. FAQ (6-8 questions) 8. Final CTA (different angle, same action) Make it responsive. Use [Tailwind / our existing design system]. If I'm using Lovable: keep the prompt focused on what the user sees, not implementation details. ``` --- ## Improving an Existing Page **Tell AI:** ``` Review our landing page at [URL or file path] and improve it: - Check: Is the headline outcome-focused or feature-focused? - Check: Is there a clear single CTA above the fold? - Check: Does social proof appear early? - Check: Does the page follow the buyer's monologue (What is this → Is it for me → How does it work → Can I trust it → What do I do)? - Rewrite any weak sections - Add missing sections (FAQ, testimonials, final CTA) ``` --- ## Performance Requirements - Load time: <2 seconds on 3G - LCP (Largest Contentful Paint): <2.5 seconds - No layout shift on load (CLS <0.1) - Lazy load everything below the fold - Hero image/video optimized aggressively --- ## Common Mistakes | Mistake | Fix | |---------|-----| | No clear CTA above the fold | One high-contrast button with specific action text | | Feature-focused headline | State the outcome the user gets, not what the product does | | "Get started" or "Learn more" CTAs | Be specific: "Create your first dashboard" | | No social proof | Add logos, user count, or testimonial — even one helps | | Missing FAQ section | Answer the 5-6 questions every buyer has | | Desktop-only design | 50%+ of traffic is mobile. Test there first. | | Trying to say everything | One page, one goal, one audience. Cut the rest. | --- ## Related Skills - **copywriting** — Write stronger headlines, CTAs, and microcopy - **conversion** — CRO techniques for higher signup rates - **seo** — Make the landing page rank for target keywords - **brand-identity-generator** — Establish visual identity before building - **beautify** — Make the page look intentionally designed
Related Skills
validate
Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders.
ux-design
Use this skill when flows feel clunky, users are confused, navigation needs planning, onboarding needs design, or accessibility needs implementation. Covers information architecture, user flows, interaction patterns, progressive disclosure, and error handling UX.
ui-patterns
Use this skill when the user needs to build a dashboard, settings page, data table, or any page layout. Also use when choosing component libraries, implementing responsive design, dark mode, or handling UI states (loading, empty, error). Covers component selection, page composition, and responsive implementation.
translate
Use this skill when the user is a domain expert (lawyer, doctor, contractor, accountant, etc.) who wants to turn their professional knowledge into a software product. Also use when the user says 'I have an idea for my industry,' 'I know this problem exists,' 'I want to build something for [profession],' or is struggling to describe what they want the software to do. Helps identify which professional pain is worth building for, then translates it into requirements AI tools can execute.
test
Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.
technical-seo
Use this skill to implement technical SEO optimizations in code — meta tags, schema markup, Core Web Vitals, crawlability, robots.txt, sitemaps, and GEO (Generative Engine Optimization) for AI search engines. This is the implementation skill — for strategy see seo, for content writing see seo-content, for auditing see seo-audit.
support
Use this skill when the user needs to create help docs, build a knowledge base, set up self-serve support, or reduce support tickets. Covers documentation strategy, help center structure, support tone, and scaling support without hiring.
social-media
Use this skill when the user needs to grow a social media presence, create content for Twitter/X, LinkedIn, or other platforms, build a founder brand, or use social media as a distribution channel. Covers platform strategy, content frameworks, posting cadence, and audience building for bootstrapped SaaS founders.
seo
Use this skill when the user needs to plan SEO content, do keyword research, build a content calendar, map search intent to page types, or create an internal linking strategy. Also use when the user says 'how do I rank higher,' 'what should I write about for SEO,' 'SEO plan,' 'what keywords should I target,' or 'how to get organic traffic.' This is the strategy and planning skill — for writing content see seo-content, for technical implementation see technical-seo, for auditing see seo-audit.
seo-content
Use this skill when the user needs to write SEO content — blog posts, landing pages, feature pages, comparison pages, how-to guides, or any content meant to rank in search and get cited by AI. Covers content briefs, humanized writing that avoids AI detection, SERP feature targeting, entity optimization, content refresh, and quality self-checks. This is the writing skill — for strategy see seo, for technical implementation see technical-seo, for auditing see seo-audit.
seo-audit
Audit a codebase for SEO and AI-answer visibility, then produce a prioritized fix-it plan. Use this skill whenever a user says things like "audit my SEO", "check my site for search visibility", "how do I rank better", "optimize for Google", "optimize for AI answers", "SEO review", "GEO audit", "run the SEO agent", or anything about improving organic traffic or search rankings. Also trigger when someone mentions wanting visibility in AI-generated answers (ChatGPT, Gemini, Perplexity, Claude). Works on any web project — static sites, Next.js, Astro, Hugo, WordPress themes, or anything that outputs HTML.
secure
Use this skill when the user needs to secure their SaaS app, implement authentication, protect user data, secure APIs, or check for vulnerabilities. Also use when the user says 'is my app secure,' 'security check,' 'I'm worried about hackers,' 'how do I protect user data,' or 'security before launch.' Covers OWASP Top 10, auth best practices, data protection, and security checklists for apps built with AI tools.