agentsclimarketplace
Sign in

Landing page critique

Skill newmindsgroup/ai-agent-skills-library/dist/skills/landing-page-critique

Use when the user wants a landing page audit, homepage critique, conversion review, website review, hero section critique, page improvement recommendations, or an explanation of why a page is not converting. Also use when the user asks to improve a page and the work should combine StoryBrand, UX, CRO, and visual hierarchy instead of a narrow copy-only or design-only pass.From its SKILL.md

Install
npx -y skills add newmindsgroup/ai-agent-skills-library --skill landing-page-critique

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

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 275 tokens by cl100k_base, as published. Nobody here has run it

Landing Page Critique

Use this skill to audit landing pages and high-conversion website pages.

Read First

  • /Users/newmindsgroup/.codex/knowledge/design-reviews/landing-page-audit-rubric.md
  • /Users/newmindsgroup/.codex/knowledge/design-reviews/page-messaging-brief.md
  • /Users/newmindsgroup/.codex/knowledge/design-reviews/visual-anti-pattern-checklist.md
  • /Users/newmindsgroup/.codex/knowledge/storybrand/index.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/avoid-patterns.md

Review Scope

  • hero clarity
  • problem and promise
  • proof and objections
  • CTA hierarchy
  • section flow
  • visual hierarchy
  • responsiveness basics
  • accessibility basics
  • overall conversion friction

Workflow

  1. Start with StoryBrand-first page logic unless the user asks for a different framework.
  2. Audit the page using the rubric.
  3. Prioritize findings by conversion risk and clarity risk.
  4. Recommend concrete rewrites or restructuring.

Outputs

  • prioritized findings
  • rewrite recommendations
  • section-order recommendations

Guardrails

  • findings first, summary second
  • do not separate copy, UX, and visual issues when they are one problem

What ships with it: 1 file

243 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,614. 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.