origin-lp-review

Evaluates landing pages through deterministic rendering measurements and independent marketing rubric scoring.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Aki2022/skills --skill origin-lp-review-aki2022
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: origin-lp-review
Source: https://github.com/Aki2022/skills/tree/main/origin-lp-review
Command: npx skills add https://github.com/Aki2022/skills --skill origin-lp-review-aki2022

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve? Landing page reviews suffer from self-assessment bias: the agent that built the page tends to mark its own work as passing, and existence checks (alt attributes, lang tags) pass even when text is unreadable on screen. This Skill separates aesthetic/layout checks into deterministic pixel-level measurement and routes subjective marketing judgment to independent reviewers who did not build the page. ## Core Features & Use Cases - Deterministic aesthetic measurement: The measure_lp.mjs script uses Playwright to render the page across viewports and color schemes, checking contrast ratios, type scales, tap targets, line length, heading orphans, first-viewport H1/CTA presence, and image cropping against documented thresholds, splitting results into disqualifying failures and warnings. - Independent marketing scoring: Three reviewers with distinct perspectives (first-time target reader, skeptical non-target, competitor comparison) score 10 rubric items from 0-4, with medians taken and rewrite suggestions required for low scores. - Gated workflow: Qualitative review only runs after deterministic checks pass, preventing wasted reviewer tokens on broken pages. - Use Case: Before publishing a landing page, run the measurement script to catch a light-mode headline with 1.1:1 contrast that existing validators missed, then have independent reviewers score whether the copy communicates the service within 3 seconds. ## Quick Start Ask the AI to evaluate your landing page by providing its URL, for example: "Review the landing page at https://example.com/lp before we publish it."

Frequently Asked Questions about origin-lp-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check landing page contrast and layout automatically?

Run the measure_lp.mjs script with the page URL to render it in Playwright across viewports and color schemes. It measures contrast ratios, font scales, tap targets, line length, and first-viewport content, exiting with code 1 when disqualifying failures are found.

How to score landing page copy quality objectively?

Use three independent reviewers with distinct perspectives (first-time reader, skeptic, competitor comparison) who score 10 rubric items from 0 to 4 against written anchors. Take the median per item and require concrete rewrite suggestions for any item scoring 2 or below.

What dependencies does the LP measurement script need?

The script requires the playwright npm package with a Chromium browser installed via npx playwright install chromium. If Playwright cannot be resolved, the script exits with code 2 and an error message rather than silently skipping.

Why does the review gate block qualitative scoring until measurements pass?

Reviewers consume tens of thousands of tokens each, and scoring a visually broken page only produces display-defect reports that contaminate copy evaluation. The gate ensures deterministic failures are fixed first, and any copy revision triggers re-measurement.

What are the known limitations of automated LP measurement?

Contrast over images uses approximate background estimation and stays a warning requiring visual confirmation. Japanese word-break detection, uncalibrated image-sunk thresholds, and headless webfont loading differences are documented as unverified or warning-level items.

When should I not use this landing page review skill?

Do not use it for non-LP web product UI evaluation, new design generation, or standalone compliance audits, which belong to other skills. If you only need deterministic measurements, call measure_lp.mjs directly from CI or hooks without the full review workflow.