webinar-funnel-teardown
Skill2 starsChanged 5 months agoMITView on GitHub
Teardown of a webinar / masterclass / VSL funnel — the registration page, show-up mechanics (reminders/replays), the webinar's content-to-pitch structure, the offer and its urgency, and the post-webinar follow-up — ending with the funnel's leaks. Use when the user shares a webinar or masterclass registration URL, or asks to "break down this webinar funnel", "analyze this masterclass", "reverse-engineer their webinar", or studies an online-course launch funnel.
In this repository14 other files it gives its agents.
- ad-creative-analysisSkill
- business-model-teardownSkill
- competitor-teardownSkill
- email-nurture-teardownSkill
- funnel-auditSkill
- icp-segmentationSkill
- landing-ux-reviewSkill
- offer-teardownSkill
- online-school-auditSkill
- positioning-messaging-auditSkill
- pricing-analysisSkill
- review-miningSkill
- seo-content-gapSkill
- social-proof-auditSkill
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 110
Do not fabricate the webinar script or the offer if you couldn't see them — mark as "not observed" and note what's needed.
- Distinctive: line 114
No invented attendance, conversion, or revenue numbers.
≈ “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
Webinar Funnel Teardown
Reverse-engineer a webinar/masterclass funnel end to end — registration, the pitch structure, the offer, and the follow-up — and find where it leaks.
What it does
Breaks down a webinar-based sales funnel (live or evergreen masterclass, VSL, or challenge that ends in a pitch) into its stages: the registration page, show-up and reminder mechanics, the webinar's content→transition→offer structure, the offer with its stack and urgency, and the post-webinar email/retargeting sequence. Ends with the biggest leaks and how to fix them. Pairs well with online-school-audit and offer-teardown.
When to use this skill
- "Break down this webinar / masterclass funnel:
<url>." - "Reverse-engineer
<creator>'s webinar." - "Analyze this free training that pitches a course at the end."
- Competitive research on course/coaching launch funnels.
Inputs needed
- Required: the registration URL (and the sales/offer page if separate).
- Helpful: whether it's live or evergreen, the niche, and — importantly — notes from the user if they attended (the webinar content itself and the pitch usually aren't observable from the page alone).
- Be honest about access: you can analyze the registration page, confirmation/ reminder emails (if provided), and the offer page. The live webinar content is often not observable — say so, and ask the user what they saw if they attended.
Method
- Registration page — the hook/promise, the "what you'll learn" bullets, the date/time or "instant access" (live vs evergreen tell), scarcity, and how much friction the opt-in has. Grade its clarity and desire.
- Show-up mechanics — confirmation page, reminder emails/SMS, replay window, "add to calendar", and any incentive to attend live. (Analyze what's provided.)
- Webinar structure (from user notes/recording if available) — map it against the classic pattern: hook → story/credibility → 3 content "secrets" (teach what, not how) → transition to the offer → value stack → price reveal & anchor → guarantee → urgency/scarcity → Q&A/close. Note which beats are present.
- The offer — what's sold, price, payment plans, bonuses/stack, guarantee, and the urgency mechanism (cart close, fast-action bonus, seat limit).
- Post-webinar follow-up — the email/retargeting sequence that closes non-buyers (replay, objection-handling, deadline, last-call). Analyze if provided.
- Find the leaks — registration conversion, show-up rate, the content→pitch transition, offer clarity, or a weak follow-up. Identify the biggest one.
Output format
# Webinar Funnel Teardown — <Brand / creator>
## TL;DR
- Funnel type (live/evergreen), the promise, how they monetize, and the #1 leak.
## 1. Registration page
- Hook/promise · learn-bullets · live vs evergreen · scarcity · opt-in friction · grade:
## 2. Show-up mechanics
- Confirmation, reminders, replay window, live incentive:
## 3. Webinar structure (observed vs inferred)
| Beat | Present? | Notes |
|------|----------|-------|
| Hook | | |
| Story / credibility | | |
| Content (the "secrets") | | |
| Transition to offer | | |
| Value stack | | |
| Price & anchor | | |
| Guarantee | | |
| Urgency / scarcity | | |
| Close / Q&A | | |
## 4. The offer
- Product · price · payment plans · bonuses · guarantee · urgency mechanism:
## 5. Post-webinar follow-up
- Sequence to close non-buyers:
## 6. Leaks & fixes
| Stage | Leak | Fix | Impact | Effort |
|-------|------|-----|--------|--------|Quality bar
- Clearly separate what you observed (registration/offer pages, provided emails) from what's inferred or came from the user's attendance notes.
- Do not fabricate the webinar script or the offer if you couldn't see them — mark as "not observed" and note what's needed.
- Flag manipulative tactics (fake live/"just started", perma-urgency, unverifiable income claims) honestly rather than praising them.
- No invented attendance, conversion, or revenue numbers.
Common mistakes to avoid
- Reviewing only the registration page and calling it a funnel teardown.
- Presenting the inferred webinar structure as if you watched it.
- Ignoring the post-webinar follow-up, where most sales actually close.
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.

