funnel-audit
Skill2 starsChanged 5 months agoMITView on GitHub
Map and critique a company's marketing/sales funnel from its public site — from first touch (ad/SEO/landing) through lead capture, nurture, and conversion — using an AARRR/awareness-to-action lens, and find the leaks. Use when the user asks to "audit the funnel", "map their funnel", "where are we losing people", "review our conversion path", or shares a site and wants the acquisition-to-conversion journey analyzed.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- Zenobia0000/dtc-copywriting-skillstheir own version, first seen Mar 20, 2026
- coleschaffer/copywritingskills-rmbctheir own version, first seen Mar 17, 2026
- indranilbanerjee/digital-marketing-protheir own version, first seen Feb 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- indranilbanerjee/digital-marketing-pro★ 934same name
- coleschaffer/copywritingskills-rmbc★ 32same name
- Zenobia0000/dtc-copywriting-skills★ 4same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- ad-creative-analysisSkill
- business-model-teardownSkill
- competitor-teardownSkill
- email-nurture-teardownSkill
- icp-segmentationSkill
- landing-ux-reviewSkill
- offer-teardownSkill
- online-school-auditSkill
- positioning-messaging-auditSkill
- pricing-analysisSkill
- review-miningSkill
- seo-content-gapSkill
- social-proof-auditSkill
- webinar-funnel-teardownSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 42
If there are multiple funnels (e.g.
- Distinctive: line 94
If the user provides real drop-off data, use it.
≈ “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.
Files
Funnel Audit
Reconstruct the path a visitor takes from first touch to customer, and pinpoint exactly where it leaks.
What it does
Maps the visible funnel — entry points, landing experience, lead capture, nurture, and the conversion step — onto a stage model (Awareness → Interest → Consideration → Conversion → Retention, i.e. AARRR-style), then diagnoses the weakest stage and recommends fixes in priority order.
When to use this skill
- "Audit this funnel:
<url>." - "Map how
<company>takes someone from visitor to customer." - "Where are we losing people in our funnel?"
- Planning a conversion-rate or lead-gen improvement.
Inputs needed
- Required: the entry URL (homepage or the specific landing page).
- Helpful: the traffic source you care about (ads vs SEO vs email), the conversion goal (signup, demo, purchase, lead), and any analytics the user has (drop-off points, conversion rates).
- If there are multiple funnels (e.g. self-serve and sales-led), ask which one.
Method
- Identify entry points — how people arrive: SEO content, paid landing pages, homepage, lead magnets. Note the dominant one.
- Walk the path stage by stage and record what happens at each:
- Awareness — the hook/first impression; message-match to the source.
- Interest — does the page build relevance and desire (problem → solution)?
- Consideration — proof, comparison, objection handling, pricing clarity.
- Conversion — the primary action: form length, CTA clarity, friction, trust at the moment of commitment.
- Retention/next step — what happens after (onboarding, email, upsell).
- Find friction and leaks — at each stage, list what would cause drop-off (unclear next step, too many asks, weak proof, slow load, mismatch).
- Locate the biggest leak — the single stage most likely losing the most people, and why.
- Prescribe fixes — concrete, per-stage, prioritized by impact vs effort.
Output format
# Funnel Audit — <Company / page>
## TL;DR
- The funnel in one line, and the #1 leak.
## Funnel map
| Stage | What happens | Strength | Friction / leak |
|-------|--------------|----------|-----------------|
| Awareness | | | |
| Interest | | | |
| Consideration | | | |
| Conversion | | | |
| Retention | | | |
## Biggest leak
- Stage:
- Why people drop here:
- Estimated impact (qualitative):
## Message-match check
- Source → landing alignment:
## Prioritized fixes
| # | Stage | Fix | Why | Impact | Effort |
|---|-------|-----|-----|--------|--------|Quality bar
- Anchor each leak to a specific, observable cause on the page.
- If the user provides real drop-off data, use it; otherwise reason qualitatively and label it as such — don't invent conversion percentages.
- Distinguish the funnel you can see (public) from steps you're inferring (e.g. the email nurture you can't observe).
Common mistakes to avoid
- Auditing one page in isolation instead of the journey across stages.
- Listing generic CRO tips not tied to this funnel's actual weak stage.
- Ignoring message-match between the traffic source and the landing page.
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
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.

