Landing page cro

Skill nahiddotai/operator-powers/plugins/operator-powers/skills/landing-page-cro

Improve an existing landing, sales, homepage, pricing, feature, or lead-capture page with prioritized copy, structure, trust, CTA, friction, and test changes.From its SKILL.md

Install

npx -y skills add nahiddotai/operator-powers --skill landing-page-cro

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

2 things to look at

27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 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.

SKILL.md

1.9 KB, 390 tokens by cl100k_base, as published. Nobody here has run it

Landing Page CRO

Improve the conversion path of an existing page while separating observations from testable hypotheses.

Job contract

Owns: page-level conversion clarity, persuasion, trust, hierarchy, friction, and experiments.
Does not own: underlying offer design (offer-builder) or voice cleanup alone (de-slop).
Required input: page copy, screenshots, files, or a URL the agent can inspect, plus the intended action when known.
Finished deliverable: prioritized page diagnosis and copy-ready changes.

Workflow

Identify page type, intended visitor, traffic source, and primary action.
Run the five-second test: what it is, who it is for, why it matters, and what to do next.
Trace message match from source to headline to proof to CTA.
Inspect value clarity, CTA hierarchy, evidence, objections, friction, scannability, mobile risks, and next-step uncertainty.
Separate confirmed problems from hypotheses that require analytics or testing.
Prioritize by likely effect, confidence, and effort.
Draft replacement copy for the highest-priority sections.

Output

# Landing Page Conversion Review

## Conversion Goal And Visitor
[What is known and assumed]

## What Is Blocking Action
[Evidence from the page]

## Priority Changes
| Priority | Change | Why | Confidence | Effort |

## Copy-Ready Replacements
[Headline, subhead, CTA, proof, objection copy]

## Test Queue
[Hypothesis, variant, metric, decision rule]

## Missing Evidence
[Analytics, traffic, research, or device checks needed]

Guardrails

Never claim a conversion lift before a real test.
Do not invent customer proof, urgency, guarantees, or performance data.
Preserve the defined offer unless the user explicitly asks to change it.

What ships with it: 1 file

225 B alongside SKILL.md

agents/

openai.yaml225 B