/market-landingCompatible with Claude, ChatGPT, Gemini, and Claude Code.
Market Landing
CRO analysis of your landing page, blocker by blocker.
What the skill does
In detail.
Runs your landing page through a CRO sieve: visual hierarchy, friction, message-audience match, proof, forms. Every conversion blocker found comes with its concrete fix, ranked by impact.
When to use it
Before sending paid traffic to a page — or when conversion rate disappoints.
Usage example
/market-landing https://mysite.com/special-offer1 · The simplest way
Copy and paste into any AI chat
This button copies the whole skill. Paste it into Claude, ChatGPT, or Gemini, then describe what you need. No installation required.
In a chat, Word or Excel files can't always be generated: you'll receive the document as structured text instead, and Claude will flag it.
Installation
3 steps to use it in Claude.ai
Download the ZIP
Click the button above. For free skills, leave your email to get the link; for premium ones, pay via Stripe then grab the link.
Open Claude.ai and create the skill
On claude.ai, open your profile (bottom left) → Customize → Skills tab → + button → Create skill. Upload the .zip you just downloaded.
Toggle it on and use the skill
The skill shows up in your list — flip the toggle. In any conversation, type the command (e.g. /market-quick followed by a URL).
Using Claude Code (terminal or app)?
The ZIP works there too: unzip it into ~/.claude/skills/ (Mac/Linux) or C:\Users\YourName\.claude\skills\ (Windows), then restart Claude Code.
In depth
How this skill really works
Market Landing produces a full CRO (Conversion Rate Optimization) analysis of a landing page, section by section, using a 7-point weighted framework: hero (25%), value proposition (20%), social proof (15%), features and benefits (15%), objection handling (10%), call-to-action (10%), and footer (5%). Each section is scored out of 10 against a documented rubric, and every conversion blocker found comes with a concrete fix ranked by priority (quick win, medium-term, strategic).
Before scoring the hero, the skill identifies which customer-journey phase the page targets (awareness, consideration, or purchase): a mismatch between the incoming traffic's intent and the hero's message is flagged as the #1 conversion killer. The skill rounds out the analysis with a form audit (field count, labels, error handling), a mobile audit (tap targets, load time), a speed-to-conversion impact table (every second lost beyond 2 seconds drops conversion by documented tiers), and A/B test hypotheses in the required format "If we [CHANGE], then [METRIC] will [IMPROVE] because [REASON]".
The full output is written to LANDING-CRO.md, with an overall CRO score out of 100, an estimate of the current conversion rate and a realistic target; the skill systematically ties every recommendation to an estimated business impact rather than a purely aesthetic change.
When to use it
- When the user provides a landing page URL and asks for conversion optimization.
- When landing page feedback, review, or an audit is requested.
- Before sending paid traffic to a page — or when conversion rate disappoints afterward.
- When the user wants to know whether the page's message actually matches the intent of the traffic reaching it (awareness, consideration, purchase).
- When prioritized, formatted A/B test hypotheses are expected, not just a list of ideas.
When not to use it
- Not for a fast first look under 30 lines — that's /market-quick.
- Not for detailed copy rewrites without the rest of the CRO audit (forms, speed, hierarchy) — /market-copy does that without the full CRO framework.
- Not for a page that isn't a conversion-focused landing page (a blog post, an about page) — the 7-point framework and its conversion-rate benchmarks are calibrated for conversion-oriented pages.
The method
The 7-point weighted CRO framework
The SKILL.md weights 7 page sections by their actual weight in the conversion decision — the hero carries 25% of the score, the footer 5%. Each section has its own checklist and its own 1-10 scoring rubric.
- Hero section (25%)
- The first screen a visitor sees; 20-35% of visitors leave without scrolling. The headline, subhead, and CTA must match the targeted customer-journey phase (awareness, consideration, purchase).
- Value proposition (20%)
- Clarity of what the product does, differentiation from alternatives, quantified benefits — evaluated via the 4U framework (useful, urgent, unique, ultra-specific).
- Social proof (15%)
- At least 2 types of social proof present (metrics, named testimonials with photos, client logos, case studies), placed near decision points, with non-rounded numbers.
- Features and benefits (15%)
- Features are translated into concrete benefits, visual hierarchy guides the eye, 3-7 key items max without overwhelming.
- Objection handling (10%)
- FAQ covering the top 3-5 objections for the page type, risk-reversal guarantees, pricing transparency.
- Call-to-action (10%)
- CTA text that describes value (not the action), a visually dominant button, supporting microcopy ("no credit card required"), the CTA repeated on long pages.
- Footer (5%)
- Final CTA present, contact or support info visible, legal notices linked, no competing link that pulls away from conversion.
Steps
Identify the page type and its benchmark
Determine which of the 8 types (lead capture, SaaS signup, e-commerce product, webinar, app download, waitlist, consultation booking, donation) applies — each has a reference "good" and "great" conversion rate.
Run the 7-point CRO framework
Score each section 1-10 against its own checklist, starting by identifying the targeted customer-journey phase for the hero.
Score the overall copy
Evaluate clarity, urgency, specificity, proof, and action orientation out of 10 each, for a copy score out of 100.
Audit form and mobile
Check field count, labels, error handling, then tap targets, readability, and mobile load time.
Assess page-speed impact
Compare load time against the documented conversion-impact table (each tier beyond 2 seconds drops conversion by a stated percentage).
Generate A/B hypotheses and the report
Phrase every test as "If we [CHANGE], then [METRIC] will [IMPROVE] because [REASON]", then write LANDING-CRO.md with the overall score, fixes ranked by effort-to-impact, and before/after wireframe suggestions.
Rules
- Always identify the targeted customer-journey phase (awareness, consideration, purchase) before scoring the hero — a traffic/message mismatch is the #1 conversion killer.
- Score each section according to its assigned weight (hero 25%, value 20%, social proof 15%, features 15%, objections 10%, CTA 10%, footer 5%) — never uniformly.
- Always tie every recommendation to an estimated business impact, not a purely aesthetic change.
- Phrase every A/B test recommendation in the required format "If we [CHANGE], then [METRIC] will [IMPROVE] because [REASON]".
- Prioritize fixes by effort-to-impact ratio, quick wins first.
- Write the full report to LANDING-CRO.md with an overall score out of 100 and an estimate of the current vs. target conversion rate.
Mistakes to avoid
- Scoring all 7 sections uniformly without accounting for their actual weight — a 5%-weight footer doesn't deserve the same treatment as a 25%-weight hero.
- Judging the hero of a Purchase-phase page as if it were an Awareness page, ignoring the targeted customer-journey phase.
- Giving vague feedback ("improve your headline") instead of the quantified before/after format the skill requires.
- Listing A/B test ideas without the required hypothesis format, or without ranking them by effort-to-impact priority.
- Declaring a conversion rate "good" or "bad" without referencing the benchmark specific to the identified page type.
What this skill doesn't do
- Does not deliver a fast scorecard under 30 lines — that's /market-quick.
- Does not provide detailed page-type-specific copy rewrites outside the CRO framework — /market-copy covers that depth of writing.
- Does not have access to real heat-map data — it provides expected-attention-zone reasoning, explicitly presented as an estimate, not real analytics.
- Does not run the A/B tests itself — it only generates the hypotheses to test; execution remains the user's job.
- Does not apply to a page that isn't conversion-oriented (a blog post, an about page) — its conversion-rate benchmarks are calibrated for landing pages.
Skill contents — 1 fichiers · 13.8 KB(SKILL.md)
Download for free