Communitygithub.com

landing-page-optimizer

Diagnose and improve landing-page relevance, trust and conversion flow.

Qu'est-ce que landing-page-optimizer ?

landing-page-optimizer is a Claude Code agent skill that diagnose and improve landing-page relevance, trust and conversion flow.

Compatible avec~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Athenous/athenous-skills/tree/HEAD/skills/landing-page-optimizer

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Landing Page Conversion Optimizer

Purpose

Diagnose and improve landing-page relevance, trust and conversion flow.

Use this Skill when

Use for the paid campaign planning, creative or conversion task described here. Confirm the campaign goal and the decision owner.

Required context

  • page URL/screenshots
  • traffic source
  • audience
  • offer
  • conversion goal
  • analytics
  • device split
  • speed/accessibility data
  • compliance

State assumptions where inputs are incomplete. Never invent performance data, platform limits, approved claims or legal clearance.

Specialized workflow

  1. Match ad/query promise to headline
  2. assess hierarchy and CTA clarity
  3. review friction, form fields, trust and objections
  4. inspect mobile, speed and accessibility evidence
  5. prioritize changes
  6. design controlled test and guardrails.

Deliverables

  • Annotated critique
  • friction map
  • revised wireframe/copy
  • test backlog
  • tracking and QA plan.

Quality gates

  • Keep the audience, offer, creative and landing-page promise consistent.
  • Verify claims, tracking, links, dates, currency and platform specifications.
  • Separate estimates from observed data; state attribution and measurement caveats.
  • Prioritize by impact, confidence, effort, risk and reversibility.

Ready-to-use workflow

Copy/paste prompt

Use landing-page-optimizer for [brand/client]. Objective: [business goal]. Audience: [target audience]. Channel/context: [platform, market and timeframe]. Brand voice/constraints: [details]. Inputs: [assets, metrics, links, examples]. Check: page URL/screenshots; traffic source; audience; offer; conversion goal; analytics; device split; speed/accessibility data; compliance. Ask one critical clarification only if required; otherwise state assumptions and deliver ready-to-use work. Do not invent performance data or brand facts.

Execution checklist

  1. Confirm brand, audience, objective, channel, format, timeframe and success measure.
  2. Review supplied assets and evidence; identify brand, platform, accessibility, legal and approval constraints.
  3. Execute the specialized workflow above. Tailor every recommendation to the platform and audience rather than mechanically reusing generic content.
  4. Produce complete assets and supporting rationale; label any claim that needs verification or approval.
  5. Provide a practical publishing/implementation checklist and measurement plan. Do not publish or change live assets without explicit approval.

Output contract

Lead with the strongest recommendation. Include:

  • Annotated critique: final-ready output with rationale and practical next step.
  • friction map: final-ready output with rationale and practical next step.
  • revised wireframe/copy: final-ready output with rationale and practical next step.
  • test backlog: final-ready output with rationale and practical next step.
  • tracking and QA plan.: final-ready output with rationale and practical next step.

Also include audience, objective, format/specifications, CTA, assumptions, sources and approval flags. Make the output usable without additional rewriting wherever possible. Mark unknowns Not provided.

Example invocation

Create landing-page-optimizer for [brand] targeting [audience]. Goal: [goal]. Channel/format: [platform and format]. Voice: [voice]. Use [provided materials]. Return finished assets plus a checklist and KPIs.

Quality check

  • Keep the audience, offer, creative and landing-page promise consistent.
  • Verify claims, tracking, links, dates, currency and platform specifications.
  • Separate estimates from observed data; state attribution and measurement caveats.
  • Prioritize by impact, confidence, effort, risk and reversibility.

Athenous MCP usage

MCP is optional. Discover exact available tools and schemas at runtime before reading or changing campaigns. Never invent campaign fields, platform integrations or write operations. Use only authorized client accounts and preserve workspace isolation. If the needed capability is unavailable, provide the plan and manual implementation steps.

Approval and safety

Before publishing, launching, editing targeting or changing spend, show the exact settings and obtain explicit confirmation. Retargeting recommendations must respect consent, privacy law and platform policy; never advise bypassing consent or targeting sensitive traits. Do not claim an action succeeded without tool confirmation.

Skills associés