mcpField
L
landing-page-critique

landing-page-critique

github.com/sylphxaiMarketing & growth153 installsUpdated today
Repository

About landing-page-critique

landing-page-critique is a marketing skill for diagnosing landing pages and planning prioritized copy and layout experiments. It evaluates the conversion argument while distinguishing positioning issues from interface polish.

Key features

  1. 01Identifies audience and conversion goal
  2. 02Evaluates messaging, proof, and demonstration
  3. 03Reviews CTA path, trust, and objections
  4. 04Separates positioning from UI polish
  5. 05Prioritizes copy and layout experiments

Use cases

  1. 01Diagnose a page for a target audience
  2. 02Find weaknesses in the conversion path
  3. 03Plan evidence-based page experiments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill landing-page-critique

After installing, type/landing-page-critiquein Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/landing-page-patterns.md

Details

From the project README

Landing Page Critique

Use this skill to turn a landing page into a clear conversion argument.

Workflow

  1. Identify audience, traffic source, product maturity, and desired conversion.
  2. Read references/landing-page-patterns.md.
  3. Evaluate message, proof, product demonstration, CTA path, objections, trust, and measurement.
  4. Separate positioning problems from UI polish problems.
  5. Produce prioritized copy/layout experiments.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not optimize persuasion by misleading users.
  • Do not add testimonials, logos, or claims that cannot be substantiated.
  • Treat SEO as distribution support, not a reason to dilute the core promise.

Output format

Audience and conversion:
Page diagnosis:

High-impact fixes:
- <rule id> <fix>

Experiment backlog:
- Hypothesis: <hypothesis>
  Change: <change>
  Measure: <metric>

Comments

Markdown supported