ads-landing

agricidaniel/claude-ads · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/agricidaniel/claude-ads --skill ads-landing
0 commentsdiscussion
summary

The #1 landing page issue in ad campaigns: does the page match the ad?

skill.md

Landing Page Quality for Ad Campaigns

Process

  1. Collect landing page URLs from active ad campaigns
  2. Read ads/references/benchmarks.md for conversion rate benchmarks
  3. Read ads/references/conversion-tracking.md for pixel/tag verification
  4. Assess each landing page for ad-specific quality factors
  5. Score landing pages and identify improvement opportunities
  6. Generate recommendations prioritized by conversion impact

Message Match Assessment

The #1 landing page issue in ad campaigns: does the page match the ad?

What to Check

  • Headline match: landing page H1 reflects ad copy headline/keyword
  • Offer match: promoted offer (price, discount, trial) is visible above fold
  • CTA match: landing page CTA matches ad's promised action
  • Visual match: consistent imagery between ad creative and page
  • Keyword match: search keyword appears naturally in page content

Message Match Scoring

Level Description Score
Exact match Headline, offer, CTA all align perfectly 100%
Partial match Headline matches but offer/CTA differs 60%
Weak match Generic page, loosely related to ad 30%
Mismatch Page content doesn't reflect ad promise 0%

Page Speed Assessment

Slow pages kill conversion rates. For every 1s delay, CVR drops ~7%.

Thresholds (Ad Landing Pages)

Metric Pass Warning Fail
LCP <2.5s 2.5-4.0s >4.0s
FID/INP <100ms 100-200ms >200ms
CLS <0.1 0.1-0.25 >0.25
Time to Interactive <3.0s 3.0-5.0s >5.0s
Page weight <2MB 2-5MB >5MB

Common Speed Issues in Ad Pages

  • Hero images not compressed (use WebP/AVIF)
  • Too many third-party scripts (chat widgets, analytics, heatmaps)
  • Render-blocking CSS/JS above fold
  • No lazy loading for below-fold content
  • Font files not preloaded

Mobile Experience

75%+ of ad clicks come from mobile. Mobile experience is critical.

Mobile Checklist

  • Tap targets: ≥48x48px with ≥8px spacing
  • Font size: ≥16px body text (no pinch-to-zoom needed)
  • Form fields: properly sized, keyboard type matches input (email, phone, number)
  • CTA button: full-width on mobile, visible without scrolling
  • No horizontal scroll
  • Images responsive and properly sized
  • Phone number clickable (tel: link)
  • No interstitials or popups blocking content on load

Trust Signals

Above-the-Fold Trust Elements

  • Company logo visible
  • Social proof (customer count, reviews, ratings)
  • Security badges (SSL, payment security, guarantees)
  • Recognizable client logos (B2B)
  • Star ratings or testimonial snippet

Below-the-Fold Trust Elements

  • Full testimonials with names, photos, companies
  • Case study highlights with specific metrics
  • Certifications, awards, accreditations
  • Privacy policy link
  • Physical address/phone number (local service businesses)

Form Optimization

Form Length Impact on CVR

Fields Expected CVR Impact Use Case
1-3 fields Highest CVR Top-of-funnel, free offer
4-5 fields Moderate CVR Mid-funnel, qualified leads
6-8 fields Lower CVR Bottom-funnel, sales-ready
9+ fields Lowest CVR Only for high-value offers

Form Best Practices

  • Pre-fill fields where possible (UTM data, known info)
  • Use multi-step forms for 5+ fields (progressive disclosure)
  • Show progress indicator on multi-step forms
  • Inline validation (don't wait until submit to show errors)
  • Error messages are clear and helpful
  • Submit button text is specific ("Get My Free Quote" not "Submit")
  • Thank you page has clear next steps

Ad-Specific Landing Page Elements

UTM Parameter Handling

  • UTM parameters captured and stored (for attribution)
  • Click IDs preserved: gclid (Google), fbclid (Meta), ttclid (TikTok), msclkid (Microsoft)
  • Parameters passed to form submissions or CRM

Dynamic Content

  • Dynamic keyword insertion in headline (Google Ads feature)
  • Location-specific content for geo-targeted campaigns
  • Audience-specific messaging (different pages for different segments)
  • A/B testing active on key elements (headline, CTA, hero image)

Conversion Tracking

  • Thank you page/event fires correctly for all platforms
  • Form submission triggers conversion event
  • Phone call tracking configured (if applicable)
  • Chat/live agent triggers tracked as micro-conversions

Landing Page Quality by Platform

Platform Key Requirement Notes
Google QS component: landing page experience Directly affects ad rank and CPC
Meta Page load speed critical Slow pages = Meta penalizes delivery
LinkedIn Professional, B2B appropriate Match LinkedIn's professional context
TikTok Mobile-first mandatory 95%+ TikTok traffic is mobile
Microsoft Desktop-optimized matters more Higher desktop % than other platforms

Output

Landing Page Assessment

Landing Page Health

Message Match:    ████████░░  XX/100
Page Speed:       ██████████  XX/100
Mobile:           ███████░░░  XX/100
Trust Signals:    █████░░░░░  XX/100
Form Quality:     ████████░░  XX/100

Deliverables

  • LANDING-PAGE-REPORT.md: Per-page assessment with scores
  • Message match analysis per ad-to-page combination
  • Page speed improvement priorities
  • Mobile experience fixes
  • Form optimization recommendations
  • Quick Wins sorted by conversion impact
how to use ads-landing

How to use ads-landing on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add ads-landing
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/agricidaniel/claude-ads --skill ads-landing

The skills CLI fetches ads-landing from GitHub repository agricidaniel/claude-ads and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ads-landing

Reload or restart Cursor to activate ads-landing. Access the skill through slash commands (e.g., /ads-landing) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.741 reviews
  • Neel Gupta· Dec 28, 2024

    Solid pick for teams standardizing on skills: ads-landing is focused, and the summary matches what you get after install.

  • Noor Wang· Dec 24, 2024

    Keeps context tight: ads-landing is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ren Rao· Dec 24, 2024

    Registry listing for ads-landing matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dhruvi Jain· Dec 12, 2024

    ads-landing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Neel Tandon· Nov 15, 2024

    ads-landing has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ren Abbas· Nov 15, 2024

    ads-landing reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ira Taylor· Nov 7, 2024

    I recommend ads-landing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Oshnikdeep· Nov 3, 2024

    Useful defaults in ads-landing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kabir Lopez· Oct 26, 2024

    Solid pick for teams standardizing on skills: ads-landing is focused, and the summary matches what you get after install.

  • Ganesh Mohane· Oct 22, 2024

    Registry listing for ads-landing matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 41

1 / 5