landing-page-critique
Skill8 starsChanged 5 months agoMITView on GitHub
Reviews a landing page for message clarity, audience fit, proof, calls to action, friction, and conversion improvements. Use when the user wants feedback on a landing page, homepage, pricing page, or signup page, asks for a website copy or CRO review, or wants to improve conversions or funnel performance.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- buildwithreef/claude-skillstheir own version, first seen Jul 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- buildwithreef/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- answerSkill
- api-to-exampleSkill
- bilingual-readerSkill
- calendar-prepSkill
- caption-assistantSkill
- chart-explainerSkill
- code-translatorSkill
- competitor-snapshotSkill
- coupon-hunterSkill
- course-fit-checkSkill
- cover-letter-builderSkill
- deal-checkerSkill
- draft-from-notesSkill
- explainSkill
- fact-checkSkill
- fix-grammarSkill
- hook-generatorSkill
- improve-writingSkill
- interview-prepSkill
- job-application-assistantSkill
- job-fit-reviewSkill
- job-offer-compareSkill
- linkedin-outreachSkill
- localize-textSkill
- meeting-follow-upSkill
- outline-builderSkill
- paper-readerSkill
- portfolio-project-reviewSkill
- product-review-summarizerSkill
- pronunciation-and-usageSkill
- regex-decoderSkill
- reply-assistantSkill
- repo-onboarderSkill
- rewrite-longerSkill
- rewrite-shorterSkill
- social-post-generatorSkill
- source-finderSkill
- source-listSkill
- study-planSkill
- style-matchSkill
- summarizeSkill
- table-to-csvSkill
- term-explainerSkill
- terminology-keeperSkill
- tone-rewriterSkill
- translateSkill
The file
Files
Landing Page Critique
Review the landing, pricing, signup, campaign, or product page the way a conversion-minded editor would — message clarity, audience fit, proof, objections, calls to action, and the friction that costs signups — with concrete fixes. Work only from what's visible on the page, in the user's selected text, or in tool results; don't critique invisible analytics like conversion rate unless the user provides them.
- Assess the headline, offer, audience clarity, proof, CTA, objections, visual hierarchy, friction, trust signals, and mobile/readability clues.
- Tie each critique to a visible page element or a missing one; separate quick wins from deeper positioning issues.
- Suggest concrete copy or structure rewrites, not generic marketing clichés (e.g. Before: "Get Started" → After: "Start your free 14-day trial — no card needed").
- Separate supported facts, tool-derived context, and your own assumptions or recommendations rather than blending them.
Return concise headings and include these sections when they fit: Overall diagnosis, What works, Friction points, Quick wins, Deeper tests, Suggested copy/structure. Preserve important names, numbers, links, dates, and currencies. Be specific but don't overclaim; if the visible context is insufficient, say what's missing and give the best supported next step. Respond in the same language as the user's request.
Example
Page (a freelancer-invoicing SaaS hero):
"The smarter way to manage your business." · Subhead: "Invoicing, payments, and reporting in one place." · CTA: "Sign up" · Below: a paragraph of feature copy, no pricing, no logos.
Critique:
Overall diagnosis: The page sells features but never names who it's for or what makes it "smarter" — a visitor can't tell in five seconds why to pick this over their current tool.
What works: The one-line scope ("invoicing, payments, reporting") is clear and concrete.
Friction points: Generic headline; no pricing or proof, so the visitor must guess at cost and trust; the CTA asks for commitment ("Sign up") before showing value.
Quick wins:
- Headline — Before: "The smarter way to manage your business." → After: "Get paid faster — invoicing built for freelancers."
- CTA — Before: "Sign up" → After: "Create your first invoice free."
Deeper tests: Add a proof strip (customer count or logos) above the fold and surface a starting price; test a 3-step "how it works" against the current feature paragraph.
No pricing, traffic, or audience data is on the page — confirm the target user before committing to the headline rewrite.
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
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.

