A free Claude skill that tears down your landing page the way a paid CRO consultant would — nine scored areas, no compliment sandwiches, and a rewrite attached to every criticism.
Nine areas, each scored out of 10, each failure shipped with the fix written out — actual copy, not directions. It leads with the biggest problem and ends with the three changes to make today.
Anyone spending money or hope on a page: local businesses running Google Ads to a quote page, service businesses whose homepage does landing-page duty, freelancers sanity-checking their own work before a launch.
Bring the goal and the traffic source — a page can't fail a goal it doesn't have.
“Why isn't my page converting?” · “Roast my landing page.” · “Tear down this page before I run ads to it.”
You paste the page copy and tell Claude it runs on Google Ads for “hail damage roof repair.” Here's the top of the teardown:
Overall: 4/10 · The one thing: a hail-damage ad lands on a page that never says “hail”
| Area | Score | Verdict in one line |
|---|---|---|
| 5-second test | 3/10 | What you do is clear; what I should do next isn't |
| Headline | 2/10 | A welcome mat, not an offer |
| CTA | 4/10 | Three competing buttons, none says what happens |
| Message match | 2/10 | Ad says emergency; page says est. 1987 |
Headline — what's wrong: “Welcome to Precision Exteriors — Quality You Can Trust” names nobody's problem. “Quality” and “trust” are the two vaguest words on the page.
The fix: “Hail damage? Your roof replaced in 5 days — and we handle the insurance paperwork.” (Outcome + timeframe + the objection everyone actually has.)
Do these three today: rewrite the headline (above), collapse to one CTA — “Get my free inspection”, and put “hail” in the first five words to match the ad.
Score, verdict, rewrite — every finding ships its fix. The full report covers all nine areas plus friction, trust, and mobile.
Option 1 · Claude Code
In your terminal, run:
npx skills add buildwithreef/claude-skills
Pick landing-page-critique from the list (or install the whole set). Done.
Option 2 · Claude.ai
Download the .zip below, then in Claude.ai go to Settings → Capabilities → Skills and upload it.
Download landing-page-critique.zipOption 3 · Manual
Copy the SKILL.md below into ~/.claude/skills/landing-page-critique/SKILL.md. That one file is the whole skill — no reference files needed.
---
name: landing-page-critique
description: Delivers a blunt, structured teardown of a landing page — hero, offer clarity, trust signals, CTA, friction, and mobile — with scores and rewritten copy for everything that fails. Use when the user asks for a landing page review, critique, or teardown, or says things like "why isn't my page converting", "roast my landing page", or "review this page".
---
# Landing Page Critique
A useful teardown is specific, scored, and ships the fix. "The headline is weak" is a tweet; "the headline is weak, here's the stronger one" is a critique.
## Ground rules
- No compliment sandwiches. Lead with the biggest problem. If something's genuinely good, say so once and move on.
- Every criticism comes with the rewrite or the fix — actual copy, not "make it clearer."
- Score each area /10 and justify the number in one line.
- Ask what the page is supposed to do (call? form? purchase?) and where traffic comes from before judging anything. A page can't fail a goal it doesn't have.
## Intake
- [ ] The page (URL, screenshot, or pasted copy — for URLs, review actual current content)
- [ ] The one conversion goal
- [ ] Traffic source (Google Ads, Facebook, organic, flyer QR code — this sets message-match expectations)
- [ ] Who the customer is and how urgent their problem is
## The teardown — nine areas, in order
**1. The five-second test.** Cover everything below the fold. From the hero alone: what is this, who's it for, what do I do next? If any answer takes thought, that's the first fix and probably the biggest one.
**2. Headline.** Must name the outcome or the problem — not the company, not a welcome. Rewrite formulas to reach for:
- Outcome + timeframe: "A new furnace installed by Friday"
- Problem you're rid of: "Never chase an invoice again"
- Specific proof: "312 Des Moines kitchens remodeled"
The vaguest word in the headline is the one to kill first ("solutions," "quality," "trusted").
**3. Call to action.** One primary CTA, repeated down the page — not three competing ones. Button text = verb + what happens: "Get my free quote" beats "Submit" beats "Learn more." Above the fold, visually loudest thing on the page. If the business runs on phone calls, the number is a CTA — clickable, huge on mobile.
**4. Offer clarity.** After 30 seconds a stranger should know: what exactly you get, what it costs (or how pricing works), what happens after you click. "Contact us to discuss your needs" is not an offer. Free quote, free inspection, $99 first visit, 10-minute callback — an offer has edges.
**5. Trust.** Reviews with full names and faces (or at least names and towns), review-platform logos with counts, licenses/certifications by number, guarantees with teeth ("on time or the service call is free"), photos of the actual team and actual work. Stock photos actively subtract trust — flag every one.
**6. Friction.** Count the form fields; every field past ~4 costs conversions — challenge each one ("do you need their address to give a quote?"). Check: does the form say what happens next? Is there a phone alternative? Any surprise steps (account creation, PDF download, "someone will reach out eventually")?
**7. Visual hierarchy.** Squint test: the eye should land on headline → proof → CTA. If everything is bold, nothing is. Walls of centered text, carousels, and auto-playing anything get flagged.
**8. Mobile.** Most local-business traffic is mobile. Check: hero readable without pinching, CTA/phone reachable with a thumb, form usable, load under ~3 seconds, no element wider than the screen.
**9. Message match.** The ad/post/QR that brought them must match the headline that greets them. Ad says "emergency AC repair," page says "Comfort solutions since 1987" → instant bounce. Score against the stated traffic source.
## Output format
```
# Teardown: [page] — Overall [X]/10
**The one thing:** [the single change worth the most, in two sentences]
| Area | Score | Verdict in one line |
|---|---|---|
| 5-second test | x/10 | |
| Headline | x/10 | |
| CTA | x/10 | |
| Offer | x/10 | |
| Trust | x/10 | |
| Friction | x/10 | |
| Hierarchy | x/10 | |
| Mobile | x/10 | |
| Message match | x/10 | |
## Findings
[per area: **What's wrong** → **The fix** (with rewritten copy)]
## Do these three today
1. ...
2. ...
3. ...
```
## What not to do
- Don't critique brand aesthetics when conversion is the goal — ugly pages with clear offers outconvert pretty ones with vague offers.
- Don't recommend A/B testing to a site with 200 visitors a month; they need bigger swings, not statistics.
- Don't pad the score to be nice. A 4 that gets fixed beats a 7 that gets framed.
---
Built by Reef — AI systems for small business → https://buildwithreef.com
Yes — this one. Landing Page Critique is a free, open-source Claude skill that tears down a page across nine scored areas — the five-second test, headline, CTA, offer clarity, trust, friction, visual hierarchy, mobile, and message match — and attaches a rewrite or concrete fix to every criticism.
Three ways: run npx skills add buildwithreef/claude-skills in your terminal and select landing-page-critique (Claude Code), upload the .zip from this page in Claude.ai under Settings → Capabilities → Skills, or copy the SKILL.md above into a folder at ~/.claude/skills/landing-page-critique/.
It rewrites. Weak headlines come back rebuilt from named formulas (outcome + timeframe, problem-you're-rid-of, specific proof), CTAs get replacement button text, and the report ends with the three changes to make today. 'Make it clearer' is banned output.
Yes. Tell it the page's one job (calls, form fills, bookings) and where visitors come from. If the homepage is doing landing-page duty for ads, it gets judged as one — that's usually where the message-match findings sting.
Yes. MIT licensed, no signup, no catch. It's published by Reef, an Iowa-based studio that builds AI systems, websites, and automation for small businesses. If you'd rather have this whole workflow running done-for-you, that's the work Reef takes on.
Websites & Conversion
This judges one page's persuasion; that one audits the whole machine.
Websites & Conversion
When the verdict is “start over,” here's the skeleton to rebuild on.
Leads & Content
The same tension-first thinking, applied to the content that feeds the page.