.claude/skills/sales-landing-page/SKILL.md
Create high-converting B2B landing pages using psychological section sequencing. Use when building landing pages for services, agencies, consultants, or B2B products. Provides 14-section framework optimized for conversion psychology.
npx skillsauth add awannaphasch2016/jousef-landing sales-landing-pageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build landing pages that convert using proven psychological sequencing.
Section sequence matters more than section content.
The psychological journey from stranger to buyer follows predictable patterns:
Each section sets up the next. Skip a section = break the chain.
Is this a landing page? ─────────────────────────────────────┐
│ │
▼ │
Is conversion the goal? ──────┬──────────────────────────────┤
│ │ │
▼ ▼ │
YES: Use this skill NO: Use frontend-design │
for aesthetics │
│
NO: Not this skill ◄───────────┘
| File | Purpose | |------|---------| | SECTION-FRAMEWORK.md | 14-section structure with psychology rationale | | COPYWRITING-PRINCIPLES.md | Tone, framing, psychological tactics | | CHECKLIST.md | Pre-launch conversion review |
| # | Section | Psychology | Must Accomplish | |---|---------|------------|-----------------| | 1 | Hero | Attention + Position | Clear value prop in 3 seconds | | 2 | Trust Strip | Credibility anchor | Specific numbers, not vague claims | | 3 | Emotional Reframe | Remove self-blame | "It's not your fault" safety | | 4 | Problem Mirror | Recognition | "This is exactly me!" moment | | 5 | Consequences | Cost of inaction | Make NOT buying painful | | 6 | False Solutions | Disqualify alternatives | "I tried that, didn't work" | | 7 | Core Differentiator | Why you're different | Architecture vs execution distinction | | 8 | Outcomes | Tangible results | Concrete before/after | | 9 | Implementation Areas | Scope clarity | What's included | | 10 | Process | How it works | 3-step simplicity | | 11 | Social Proof | Testimonials | Company logos + quotes | | 12 | ROI/Urgency | Decision pressure | Cost-per-day of inaction | | 13 | FAQ | Objection handling | Top 5-7 objections | | 14 | Final CTA | Close | Single clear action |
See SECTION-FRAMEWORK.md for detailed requirements.
DON'T: "We might be able to help you improve..."
DO: "Your margins are bleeding. Here's why."
Before presenting your solution, disqualify what they've already tried:
"You've probably tried:
- Hiring more people (margins got worse)
- Adding tools (complexity increased)
- Piecemeal automation (created new problems)
None of these address the root cause..."
See COPYWRITING-PRINCIPLES.md for complete tactics.
| Skill | Relationship | |-------|--------------| | template-cloning | Use for implementation mechanics | | frontend-design | Use for visual polish after content is solid | | config-driven-content | Structure content.ts around these 14 sections |
Recommended workflow:
sales-landing-page to define content strategytemplate-cloning to set up technical structurefrontend-design for visual refinementWRONG: "Let's make it look beautiful first"
RIGHT: "Let's nail the psychological sequence, then polish"
WRONG: "We help businesses grow"
RIGHT: "More margin. More capacity. Without hiring."
WRONG: Hero → Solution → CTA
RIGHT: Hero → Trust → Blame-removal → Problem → Consequences → Solution → CTA
WRONG: FAQ with 3 generic questions
RIGHT: FAQ addressing the 5-7 actual objections preventing purchase
Before launching, run through CHECKLIST.md to verify:
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
testing
Write comprehensive tests following project conventions (tiers, patterns, anti-patterns). Use when writing tests, improving test coverage, fixing failing tests, or reviewing test quality.
content-media
Clone and customize existing templates (landing pages, dashboards, admin panels) with style extraction, config-driven content, and theme customization
development
Systematic investigation and root cause analysis. Use when debugging persistent issues, understanding complex systems, or before making architectural decisions.