Landing Page logo

Landing Page

Community
boraoztunc
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.

Overview

Publisherboraoztunc
Repositoryskills
Skill namelanding-page
Stars
422
Forks
63
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by boraoztunc on GitHub. Read the source before you install it.

Installation

Install the Landing Page AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/boraoztunc/skills/tree/main/landing-page
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/boraoztunc/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/landing-page .claude/skills/landing-page
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Landing Page in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Landing Page on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Landing Page is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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?

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Landing Page AI skill do?

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.

Why use Landing Page on TypingMind?

Because you install it once and use it with any model. Landing Page is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Landing Page in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/boraoztunc/skills/tree/main/landing-page. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Landing Page?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Landing Page?

As many as you like. As long as a model supports skills, you can use Landing Page with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Landing Page AI skill free?

Yes. It is published on GitHub by boraoztunc under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇