Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsLanding Page Critique: P0–P2 Conversion Fix List
Unlike generic CRO prompts: returns a prioritized P0–P2 conversion fix list with rewrite briefs — no invented conversion lifts.
$5
Landing Page Critique: P0–P2 Conversion Fix List
Example session with this skill installed
goal: Get signups for a free trial of a React component library
audience: Frontend developers
offer: UI components for enterprise dashboards
page_content: Hero: Build faster. Subhead: The best components. Button: Start. FAQ: Is it free? Yes.
- Read your context and instructions
- Compiled the landing page critique
I have analyzed the provided landing page copy for the React component library. The critique focuses on the lack of specific value propositions and structural gaps in the current hero and FAQ sections.
Landing critique: React Component Library (Untitled)
Goal (CTA): Get signups for a free trial
Audience: Frontend developers
Offer: UI components for enterprise dashboards
Generated: 2024-05-24 · Critique draft — not a CRO performance guarantee
1. Snapshot
The current copy is too generic for a developer audience. "Build faster" is a commodity claim that lacks technical depth. The biggest blocker is the lack of visual or technical proof (e.g., code snippets, framework compatibility) and a weak value proposition that doesn't address enterprise-specific pain points like accessibility or theming.
2. Section map
| # | Section | Job it should do | Status |
|---|---|---|---|
| 1 | Hero | Define the specific tool and primary benefit | Weak |
| 2 | Features | Explain enterprise utility (e.g., accessibility) | Missing |
| 3 | FAQ | Remove friction regarding pricing/setup | Clear |
3. Dimension scores (qualitative)
| Dimension | Score (1–5) | Note |
|---|---|---|
| Offer clarity | 2 | "Best components" is vague; doesn't specify React. |
| Audience relevance | 2 | Lacks technical terminology common in dev tools. |
| Hierarchy | 3 | Simple structure, but missing middle-funnel proof. |
| Proof / credibility | 1 | No logos, testimonials, or code previews. |
| CTA clarity | 4 | "Start" is clear but lacks a low-friction hook. |
| Objection handling | 3 | FAQ addresses the cost, but not the tech stack. |
4. Ranked findings
Generic Headline — "Build faster" is used by every dev tool. Impact: High. Fix: Mention React and enterprise dashboard focus.
2.
Missing Proof — No mention of bundle size or TS support. Impact: High. Fix: Add a "Technical Specs" or "Built for" section.
3.
Vague Subhead — "The best components" is a subjective claim. Impact: Med. Fix: Quantify the library size or specific use cases.
5. Rewrite priorities
| Priority | Where | Change | Suggested rewrite direction |
|---|---|---|---|
| P0 | Hero Headline | Replace "Build faster" | "Production-ready React components for data-heavy dashboards." |
| P0 | Subhead | Define the "Best" | "50+ accessible, TypeScript-first components optimized for enterprise scale." |
| P1 | CTA | Refine "Start" | "Start your 14-day free trial — no card required." |
6. Mini rewrites
DRAFT — brand to approve
- Headline: Ship enterprise dashboards in days, not months.
- CTA: Get Started with 50+ Components.
7. Test ideas
- A/B test a code snippet vs. a UI screenshot in the hero section.
- Test a "Copy npm install" button vs. a "Start trial" button for initial engagement.
8. Open questions
- Does the library support Tailwind CSS or Styled Components?
- Is there a specific enterprise sector (e.g., Fintech, Healthcare) being targeted?
9. Suggested next step
Add a technical proof section (e.g., "Built with TypeScript, 0 dependencies") and replace the generic hero copy with the P0 rewrite directions to improve developer trust.
Connects securely to your tools. The creator never sees your data.
About this skill
Write it → Copy; review it → Critique.
Unlike generic "audit my landing page" prompts, this skill returns a prioritized P0–P2 conversion fix list with concrete rewrite briefs. It does not invent conversion-rate lifts, A/B win rates, or traffic forecasts.
Sample output (excerpt — Harborline Tools pricing page critique, Generated: 2026-10-16):
| Priority | Area | Issue | Fix brief |
|---|---|---|---|
| P0 | Hero CTA | Primary button below fold on mobile | Move "Start free" into sticky header; keep secondary "See pricing" |
| P0 | Social proof | No named customers above fold | Add 3 logo row + one quantified outcome quote |
| P1 | Offer clarity | Plan differences buried in FAQ | Add 3-column plan comparison under hero |
| P2 | Microcopy | Form error states generic | Rewrite inline errors to name the missing field |
Works in Claude Code, Cursor and Codex · evidence-only critique · v1.1, updated Oct 2026 · no conversion guarantees · questions answered via Agensi messages · More Cygnix Labs tools: https://apify.com/cygnix_labs
Vague "make it convert better" requests waste development and design time. This skill turns raw landing page copy or outlines into a structured conversion critique and prioritized rewrite list. It identifies clarity gaps, structural issues, and friction points before you commit to code.
What it does
- Restructures hierarchy by mapping sections against their specific conversion jobs.
- Scores dimensions including offer clarity, audience relevance, proof, and friction using a qualitative 1-5 scale.
- Ranks findings by impact, providing evidence-based issues and specific fix directions.
- Prioritizes rewrites into P0, P1, and P2 tiers to focus efforts on high-leverage elements like headlines and CTAs.
- Proposes test hypotheses for A/B testing or qualitative research without fabricating performance data.
How it works
- Supply the page content, primary goal, target audience, and offer details.
- The skill analyzes the copy against conversion principles like objection handling and risk reversal.
- It produces a detailed report with a section map, dimension scores, and a prioritized rewrite table.
Frameworks & tools
This skill is platform-agnostic and works with copy from any web framework or CMS, including React, Next.js, Shopify, and Webflow.
Why this beats prompting it yourself
Generic prompts often result in sycophantic praise or generic marketing fluff. This skill enforces a rigorous, evidence-based critique that focuses on friction and hierarchy, ensuring you get actionable technical and copy requirements rather than vague suggestions.
Use cases
- Reviewing high-stakes campaign landing pages before deployment.
- Auditing existing SaaS homepages during a redesign phase.
- Converting raw founder notes into a structured copy brief for developers.
- Identifying missing trust signals or weak CTAs in e-commerce product pages.
Known limitations
Does not perform live UX testing, heatmap analysis, or accessibility audits. Requires manual verification of brand voice and regulated claims.
Pairs well with (Cygnix Labs, on Agensi):
- Keyword Research — Clusters + Intent Brief: find and cluster keywords
- Keyword Gap Analysis: keywords competitors rank for and you don't
- SERP Intent Mapper: match each keyword to the right page type
- Topical Authority Map: pillar, clusters and internal links
- SEO Content Brief (free): writer-ready brief for any keyword
- Content Refresh Audit: fix pages that are losing Google traffic
- Local SEO Keyword Pack / Local SEO Audit: for local businesses
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago