agentsclimarketplace

Landing page review

Skill cognyai/claude-code-marketing-skills/skills/landing-page-review

Marketing skills for Claude Code — SEO audits and implementation, ad analysis, ad optimization. Free skills need no account. $9/mo for live Search Console, Bing & LinkedIn data.

Install
npx -y skills add cognyai/claude-code-marketing-skills --skill landing-page-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

CRO review of a landing page with specific conversion recommendations

SKILL.md

2.4 KB, 563 tokens by cl100k_base, as published. Nobody here has run it

Landing Page Review

Analyze a landing page for conversion optimization — messaging, layout, trust signals, and CTA effectiveness.

Usage

/landing-page-review example.com/pricing — review the given page

Steps

1. Fetch and analyze the page

Use WebFetch to load the URL. Extract:

  • Headline and subheadline text
  • CTA buttons (text, placement, count)
  • Value proposition clarity
  • Above-the-fold content
  • Page structure (sections, flow)

2. Evaluate messaging

Score each element:

  • Headline clarity (1-10): Does it immediately communicate what you get?
  • Value prop specificity (1-10): Numbers > vague claims
  • CTA strength (1-10): Action-oriented, specific, visible
  • Social proof (1-10): Testimonials, logos, stats
  • Urgency/scarcity (1-10): Reason to act now

3. Check trust signals

Look for:

  • Customer logos or testimonials
  • Security badges / certifications
  • Pricing transparency
  • Contact information
  • Privacy policy / terms links
  • Case studies or results

4. Analyze form/CTA friction

If there's a form:

  • Number of fields (fewer = higher conversion)
  • Field labels and placeholder text
  • Submit button text (specific > generic)
  • Error handling
  • Privacy reassurance near form

5. Mobile assessment

Check:

  • Mobile viewport optimization
  • Touch target sizes
  • Content readability on small screens
  • CTA visibility without scrolling

6. Competitive comparison

WebSearch for 2-3 competitors and briefly compare:

  • How do their landing pages differ?
  • What trust signals do they use?
  • How is their CTA different?

7. Report

Landing Page Review: [URL]
Conversion Score: X/100

Messaging: X/30
- Headline: [score] — [specific feedback]
- Value prop: [score] — [specific feedback]
- CTA: [score] — [specific feedback]

Trust: X/30
- Social proof: [score]
- Credibility signals: [score]
- Transparency: [score]

UX: X/20
- Form friction: [score]
- Mobile: [score]
- Load speed: [score]

Differentiation: X/20
- vs [Competitor 1]: [comparison]
- vs [Competitor 2]: [comparison]

Top 5 Changes (in priority order):
1. [Specific change with expected impact]
2. ...
3. ...
4. ...
5. ...

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most design frontend skills give in 563 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • Fetch the URL using WebFetch
  • Extract the headline, subheadline, and CTA buttons
  • Score messaging elements on a one to ten scale
  • Check for customer logos, testimonials, and security badges
  • Analyze form and CTA friction
  • Assess mobile viewport optimization and touch target sizes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.