Landing Pages Claude Skills — Development skill for Claude Code

26 Claude Skills for Landing Pages

A pack of 26 Claude Skills for diagnosing landing pages that get traffic and do not convert: message match, offer clarity, proof, objections, forms, mobile, pricing, page length, overlays, accessibility and the Google Ads landing page experience rating.

Each skill is a self-contained `SKILL.md` with explicit triggers, required inputs, an analysis workflow, decision rules, a worked example, an output format and guardrails. Drop them into Claude Code and they activate on their own when what you are doing matches the description.

Every skill is data-first. They read what you give them. None of them log into an account, change a page or touch a budget.

Install

Claude Code

git clone https://github.com/mardab96/landing-pages-claude-skills.git
mkdir -p ~/.claude/skills
cp -r landing-pages-claude-skills/*-* ~/.claude/skills/

Start a new Claude Code session. That is it. Every skill is self-contained: none of them reads a file outside its own folder, so there is nothing else to copy and nothing to break if you install only the ones you want.

For a single project instead of your whole account, copy into `.claude/skills/` inside the project.

Any other Claude environment

The skills are plain Markdown with YAML frontmatter. Paste the contents of a `SKILL.md` into context when you want that skill.

Start here

**`landing-page-triage`.** Ask for it by name, or just say the page gets traffic and does not convert and you do not know why.

It runs no diagnosis of its own. It asks five questions to find out what evidence you actually have, then names at most three skills to run, in order, and says which ones it is deliberately skipping and why. Twenty six skills produce twenty six opinions ranked by nothing; triage exists so that does not happen.

If the problem is already named, skip it and go straight to the skill that owns that question.

What is inside

Diagnosing the page you have

| # | Skill | Folder