agentleFS
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/funnel-message-match-auditor/SKILL.md

funnel-message-match-auditor

Skill4 starsChanged 6 months agoMITView on GitHub

Compare ad copy, landing page headline, form, thank-you page, and sales script to flag disconnects that hurt conversion quality. Use when diagnosing low conversion rates or poor lead quality.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When diagnosing low landing page conversion rates despite high ad CTR.

    line 12
  2. Distinctive:

    When leads are unqualified or confused about the offer.

    line 13
  3. Distinctive:

    When launching a new funnel to ensure consistency before spending ad budget.

    line 14
  4. Distinctive:

    When reviewing the entire customer journey from click to close.

    line 15
  5. Distinctive:

    Map the Journey: Document the exact path a user takes from seeing the ad to the final conversion event.

    line 26
  6. Distinctive:

    Review the Landing Page: Check if the headline immediately reinforces the ad's promise.

    line 28
  7. Distinctive:

    Inspect the Form: Ensure the form fields align with the perceived value of the offer (e.g., don't ask for 10 fields for a simple checklist).

    line 29
  8. Distinctive:

    Check the Thank-You Page: Verify that the next steps are clear and logically follow the initial conversion.

    line 30
  9. Distinctive:

    Review Follow-Up: Ensure the sales script or email sequence references the original offer and addresses objections sequentially.

    line 31
  10. Distinctive:

    If the ad promises something completely different from the landing page, flag it as a critical error requiring immediate attention.

    line 47
  11. Distinctive:

    If the sales script contradicts the initial offer, escalate to the user for clarification.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Funnel Message-Match Auditor

Purpose

Compare ad copy, landing page headline, form, thank-you page, and sales script to flag disconnects that hurt conversion quality. Ensure offer continuity and objection sequencing throughout the funnel.

When to Use This Skill

  • When diagnosing low landing page conversion rates despite high ad CTR.
  • When leads are unqualified or confused about the offer.
  • When launching a new funnel to ensure consistency before spending ad budget.
  • When reviewing the entire customer journey from click to close.

Inputs Required

  • Ad copy and creative (or a representative sample).
  • Landing page URL or copy.
  • Lead form fields and copy.
  • Thank-you page URL or copy.
  • Sales script or follow-up sequence (if available).

Step-by-Step Workflow

  1. Map the Journey: Document the exact path a user takes from seeing the ad to the final conversion event.
  2. Analyze the Ad: Identify the core promise, hook, and offer presented in the ad.
  3. Review the Landing Page: Check if the headline immediately reinforces the ad's promise. Evaluate the offer continuity.
  4. Inspect the Form: Ensure the form fields align with the perceived value of the offer (e.g., don't ask for 10 fields for a simple checklist).
  5. Check the Thank-You Page: Verify that the next steps are clear and logically follow the initial conversion.
  6. Review Follow-Up: Ensure the sales script or email sequence references the original offer and addresses objections sequentially.

Output Format

Provide a structured audit report containing:

  • Journey Map: A brief overview of the funnel steps.
  • Message Match Score: An assessment of consistency across the funnel.
  • Disconnects Identified: Specific areas where the message breaks down or changes unexpectedly.
  • Friction Points: Areas where the user experience is confusing or overly demanding.
  • Recommendations: Actionable steps to fix disconnects and improve continuity.

Decision Rules

  • Always ensure message match between the ad, headline, landing page, lead form, and follow-up sequence.
  • The landing page headline must be a logical continuation of the ad's hook or promise.
  • The offer must remain consistent throughout the funnel; do not bait-and-switch.

Escalation Rules

  • If the ad promises something completely different from the landing page, flag it as a critical error requiring immediate attention.
  • If the sales script contradicts the initial offer, escalate to the user for clarification.

Templates & Resources

  • checklists/message-match-audit.md: Checklist for reviewing funnel consistency.
  • templates/audit-report.md: Template for presenting audit findings.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.