Agent skill
sales-landing-page
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/sales-landing-page
SKILL.md
Sales Landing Page Skill
Build landing pages that convert using proven psychological sequencing.
When to Use This Skill
- Building landing pages for B2B services or products
- Creating pages for agencies, consultants, coaches
- Designing high-ticket offer pages
- Any page where conversion matters more than aesthetics
Core Principle
Section sequence matters more than section content.
The psychological journey from stranger to buyer follows predictable patterns:
- Capture attention (Hero)
- Build trust (Social proof)
- Create emotional safety (Remove blame)
- Mirror their problem (Recognition)
- Amplify consequences (Cost of inaction)
- Disqualify alternatives (False solutions)
- Present your approach (Differentiator)
- Show outcomes (Results)
- Explain the how (Process)
- Prove it works (Testimonials)
- Create urgency (ROI/Decision pressure)
- Handle objections (FAQ)
- Close (Final CTA)
Each section sets up the next. Skip a section = break the chain.
Quick Decision Tree
Is this a landing page? ─────────────────────────────────────┐
│ │
▼ │
Is conversion the goal? ──────┬──────────────────────────────┤
│ │ │
▼ ▼ │
YES: Use this skill NO: Use frontend-design │
for aesthetics │
│
NO: Not this skill ◄───────────┘
Files in 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 Framework Overview
| # | 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.
Key Copywriting Principles
Tone: High-Conviction Consulting
DON'T: "We might be able to help you improve..."
DO: "Your margins are bleeding. Here's why."
Problem-Agitate-Solve (PAS)
- Problem: Name their pain specifically
- Agitate: Show consequences of ignoring it
- Solve: Present your approach as the logical answer
False Alternative Disqualification
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.
Integration with Other Skills
| 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:
- Use
sales-landing-pageto define content strategy - Use
template-cloningto set up technical structure - Use
frontend-designfor visual refinement
Anti-Patterns
1. Aesthetics Before Psychology
WRONG: "Let's make it look beautiful first"
RIGHT: "Let's nail the psychological sequence, then polish"
2. Generic Hero
WRONG: "We help businesses grow"
RIGHT: "More margin. More capacity. Without hiring."
3. Skipping Problem Mirror
WRONG: Hero → Solution → CTA
RIGHT: Hero → Trust → Blame-removal → Problem → Consequences → Solution → CTA
4. Weak Objection Handling
WRONG: FAQ with 3 generic questions
RIGHT: FAQ addressing the 5-7 actual objections preventing purchase
Checklist Reference
Before launching, run through CHECKLIST.md to verify:
- All 14 sections present in correct order
- Each section accomplishes its psychological goal
- Copywriting follows high-conviction tone
- Social proof uses specific numbers
- CTA appears 3+ times throughout page
- Mobile experience maintains psychological flow
Related Resources
- SECTION-FRAMEWORK.md - Detailed 14-section breakdown
- COPYWRITING-PRINCIPLES.md - Writing tactics
- CHECKLIST.md - Pre-launch verification
- template-cloning skill - Technical implementation
- frontend-design skill - Visual polish
- docs/guides/config-driven-content.md - Content architecture
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?