landing critique pack

    1

    Transforms landing page copy into prioritized conversion critiques and rewrite briefs for developers and founders.

    $12

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    landing critique pack

    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 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

    #SectionJob it should doStatus
    1HeroDefine the specific tool and primary benefitWeak
    2FeaturesExplain enterprise utility (e.g., accessibility)Missing
    3FAQRemove friction regarding pricing/setupClear

    3. Dimension scores (qualitative)

    DimensionScore (1–5)Note
    Offer clarity2"Best components" is vague; doesn't specify React.
    Audience relevance2Lacks technical terminology common in dev tools.
    Hierarchy3Simple structure, but missing middle-funnel proof.
    Proof / credibility1No logos, testimonials, or code previews.
    CTA clarity4"Start" is clear but lacks a low-friction hook.
    Objection handling3FAQ 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

    PriorityWhereChangeSuggested rewrite direction
    P0Hero HeadlineReplace "Build faster""Production-ready React components for data-heavy dashboards."
    P0SubheadDefine the "Best""50+ accessible, TypeScript-first components optimized for enterprise scale."
    P1CTARefine "Start""Start your 14-day free trial — no card required."

    6. Mini rewrites

    DRAFT — brand to approve

    1. Headline: Ship enterprise dashboards in days, not months.
    2. 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.

    What you get

    Audit hero sections for clarity and developer-focused value propositions.Identify missing trust signals and social proof elements in page structures.Generate prioritized rewrite tables for P0/P1 conversion fixes.Structure raw founder notes into professional landing page outlines.

    About this skill

    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

    1. Supply the page content, primary goal, target audience, and offer details.
    2. The skill analyzes the copy against conversion principles like objection handling and risk reversal.
    3. 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.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    What's inside

    Frequently Asked Questions