Install in Claude Code
Copygit clone --depth 1 https://github.com/FerroxLabs/wayland /tmp/convert-webinar-reg-page && cp -r /tmp/convert-webinar-reg-page/resources/bundled-extensions/business-conversion/skills/convert-webinar-reg-page ~/.claude/skills/convert-webinar-reg-pageThen start a new Claude Code session; the skill loads automatically.
Definition
SKILL.md
# Convert Webinar Registration Page - The Reg Page
> *"A webinar reg page has two jobs, not one. Get the registration. Get the show-up. Most pages optimize for the first and ignore the second - which is why most webinars run 18% live attendance. The Method does both."*
This skill builds the webinar registration page: Method-applied above-fold copy, time/date anchoring, three-bullet curiosity stack, and the show-up cues that lift live attendance.
## When to Use
Trigger phrases: `webinar registration page`, `webinar reg page`, `register for webinar`, `masterclass registration`, `free training registration`, `/convert webinar-reg <event>`.
Use when:
- The user has a scheduled live webinar (or an evergreen / "just-in-time" loop simulating live).
- A registration page needs to convert *and* drive show-up.
## When NOT to Use
- **The webinar script itself** → `/funnel conviction-webinar`.
- **Generic opt-in for a downloadable** → `/convert lead-magnet-page` or `/convert squeeze-page`.
- **Post-registration thank-you / calendar page** → `/convert thank-you-page`.
- **Replay / encore page after the live** → handled by the email pack + a thank-you-style template.
## Inputs
Required:
1. **Webinar title** + **the big promise** (one specific outcome the attendee will have at the end).
2. **Date/time** (or "starts in X minutes" if evergreen).
3. **Presenter name + Drive-By bio.**
4. **One person + Nerve.**
5. **Form destination + post-registration URL** (usually the thank-you page with calendar add + reminder setup).
Optional:
- **Attendance bonus** - something attendees get only if they show up live (drives show-up dramatically).
- **Brand colors / logo / presenter headshot.**
- **`out_path`** - defaults via `build_report_path`.
## Workflow - All Eight Method Phases
### Phase 0 - Four Questions
- **Why You?** - Why this *specific* webinar matters to this reader, this week.
- **Why Me?** - Drive-By presenter credibility.
- **Why This?** - Why this approach / mechanism / framework taught in the webinar.
- **Why Now?** - Real (the live date) + the attendance bonus + the cost of waiting.
### Phase 1 - Temperature
Webinar reg pages run **Cool to Warm**. For Ice Cold traffic, route through a bridge page first. Page length 400–900 words.
### Phase 2 - Four-Layer Open (call `convert-open`)
Compressed:
- Layer 1 = Nerve Strike headline that names the outcome.
- Layer 2 = Side Door subhead - the casual "I'm going to walk you through..." frame.
- Layer 3 = Skin in the Game in one paragraph (presenter's qualification to teach this).
- Layer 4 = Fingerprint as a one-line aside.
### Phase 3 - Three Locks
- **Want** = the post-webinar state.
- **Trust** = presenter Drive-By + one Anecdote.
- **Excuse** = "free, 60 minutes, you can leave anytime - and there's an attendance bonus for staying live."
### Phase 4 - Bullets (call `convert-bullets`)
The classic webinar reg-page bullet stack: **3 bullets**. One Keyhole, one Snapshot, one Flip. Each one is a curiosity gap that only the webinar resolves.
- *"Why everything you've been told about [X] is actually backwards - and the simple framework that fixes it in 20 minutes."* (Flip)
- *"How [name] used the [thing] to [result] - without [common requirement]."* (Snapshot)
- *"The [unexpected thing] that quietly determines whether [outcome] is even possible. (Slide 14.)"* (Keyhole)
Three. Not five. Not ten. Three is the canonical webinar bullet count for a reason - more dilutes curiosity.
### Phase 5 - Proof (call `convert-proof`)
One Anecdote or Receipt + one Drive-By for the presenter. Heavy proof distracts from the date/time anchor.
### Phase 6 - Cascade Close (call `convert-close`)
Compact:
- Stack - date, time, duration, attendance bonus.
- Vision - what they'll have at the end of the 60 minutes.
- Math - "free + your time."
- Safety Net - "you can leave anytime, no replay pressure."
- Door - the registration form button.
### Phase 7 - Greased Chute
The eye must move: headline → date/time → 3 bullets → form → presenter bio. Five movements, no detours.
### Phase 8 - Voice + Bullshit Filter
The biggest filter test: *"Is the big promise something I can actually deliver in 60 minutes, or is it bait?"* Over-promising on the reg page tanks both show-up *and* the post-webinar offer's conversion. Promise what you can deliver.
## Section Architecture
| # | Section | Purpose |
|---|---------|---------|
| 1 | Pre-headline (date/time + "live" anchor) | Time framing |
| 2 | Headline (big promise) | Open Layer 1 |
| 3 | Subhead (Layers 2–3) | Side Door + Skin |
| 4 | Date/time/duration block | Anchor + countdown |
| 5 | Three bullets | Curiosity stack |
| 6 | Registration form | Door |
| 7 | Presenter bio block | Trust anchor |
| 8 | Attendance bonus reminder | Show-up driver |
## HTML/CSS Reference Implementation
```html
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>{{WEBINAR_TITLE}} - {{BRAND}}</title>
<meta name="description" content="{{META_DESCRIPTION}}">
<meta property="og:title" content="{{WEBINAR_TITLE}}">
<meta property="og:description" content="{{META_DESCRIPTION}}">
<meta property="og:type" content="website">
<meta property="og:image" content="{{OG_IMAGE_URL}}">
<style>
:root{--ink:#0e1116;--ink-soft:#3a3f47;--paper:#fbfaf6;--accent:#c0392b;--accent-ink:#fff;--rule:#e6e2d8;--max:680px}
*,*::before,*::after{box-sizing:border-box}
body{margin:0;font:18px/1.55 -apple-system,BlinkMacSystemFont,"Helvetica Neue",Arial,sans-serif;color:var(--ink);background:var(--paper)}
main{max-width:var(--max);margin:0 auto;padding:24px 20px 64px}
.pre-h{font-size:13px;color:var(--accent);text-transform:uppercase;letter-spacing:.1em;font-weight:700;margin:0 0 8px}
h1{font-size:clamp(28px,5.5vw,42px);line-height:1.16;margin:0 0 14px}
h2{font-size:22px;margin:32px 0 12px}
p{margin:0 0 16px}
p.subhead{font-size:20px;cMore from this repository
architectureSkill
|
bump-versionSkill
Use when bumping the Wayland version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release.
fix-issuesSkill
|
fix-sentrySkill
|
i18nSkill
|
oss-prSkill
Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.
pr-automationSkill
|
pr-fixSkill
|