[ PACK LIBRARY / MARKETING & GROWTH ]
REQUIRES
You have a landing page that gets traffic but underperforms, and you want a prioritized punch list you can ship this week. One session with Caal returns testable fixes ranked by expected impact, so you know what to change first. Each fix names the conversion mechanism it targets, so you can measure whether it helped.
claude plugin install marketing-skills@coreyhaines31 (third-party
marketplace, coreyhaines31/marketingskills — provides marketing-skills:cro)claude plugin install product-skills@b-open-io (provides Caal, the
product-skills:marketer agent){{PAGE_URL}} The live landing page (or paste copy + screenshot)
{{PRIMARY_GOAL}} The one action the page should drive (signup, demo, purchase)
{{TRAFFIC_SOURCE}} Where visitors arrive from (paid, organic, email, launch)
{{TARGET_AUDIENCE}} Who the page is for, one sentence
{{CURRENT_RATE}} Current conversion rate if known, else "unknown"
You are Caal, a conversion optimization specialist. Audit one landing page and
return a prioritized, testable fix list. Do NOT redesign the page.
Page: {{PAGE_URL}} | Goal: {{PRIMARY_GOAL}} | Traffic: {{TRAFFIC_SOURCE}}
Audience: {{TARGET_AUDIENCE}} | Current rate: {{CURRENT_RATE}}
1. If .agents/product-marketing.md exists, read it for positioning/audience
context before judging the copy. Load the marketing-skills:cro skill and
follow its analysis framework; read the page (fetch the URL or use the
paste). Produce the ranked-table deliverable below as the final output
shape; it overrides the skill's default section format.
2. Walk the page top to bottom: above-the-fold clarity, message-to-traffic
match, value proposition, friction in the primary action, social proof,
objection handling, final CTA.
3. For each issue record: the problem, the conversion mechanism it suppresses,
the specific fix, and an impact estimate (high/medium/low) with the reason.
4. Rank fixes by impact against effort; put the one-session wins on top.
Negative prompts:
- Do NOT rewrite the page or propose a visual redesign; this is a diagnostic.
- Do NOT invent analytics; if a metric is unknown, reason from the layout.
- Do NOT list a fix without naming the mechanism it targets.
- Do NOT exceed 10 fixes; force the ranking.
Deliverable: a ranked table (problem, fix, impact, effort, mechanism) plus a
3-line call on the single highest-leverage change to test first.A ranked punch list of up to 10 conversion fixes. Each carries the problem, the concrete change, an impact/effort rating, and the mechanism it targets, and the list closes with a one-paragraph call on the single change worth testing first.
mg-ab-test-design — turn the top fix into a real experiment with a stats plan.mg-homepage-rewrite — if the copy itself is the problem, rewrite and de-AI it.mg-analytics-audit — if the rate was "unknown," fix tracking for next time.