sales-page-copywriting
Generate battle-tested sales page copy through hostile validation, output only polished final copy
What this skill does
# SALES PAGE COPYWRITING - HOSTILE VALIDATION SYSTEM ## CRITICAL OUTPUT INSTRUCTION **YOU MUST OUTPUT ONLY THE FINAL POLISHED WEBSITE COPY TO THE USER.** - Do NOT show the user your internal validation process - Do NOT show hostile reviewer feedback to the user - Do NOT show the before/after revision process - Do ALL validation work internally - ONLY output the final polished website copy document --- ## PHASE 1: INPUT CAPTURE & STRATEGIC FOUNDATION When user provides a product idea or business concept, **silently extract and document internally**: ### CORE PRODUCT DNA: - What it is (in one sentence a 10-year-old would understand) - What problem it solves (the specific pain, not the generic category) - Who it's for (psychographic more than demographic) - What makes it different (the actual differentiator, not marketing fluff) - What you want visitors to do (the primary conversion goal) ### MARKET CONTEXT: - Top 3 competitors and their messaging approach - Common objections in this product category - Typical buyer journey complexity (impulse vs. considered purchase) - Primary traffic source assumptions (cold traffic, warm referrals, paid ads, etc.) **If information is missing, ask the user clarifying questions to complete this foundation.** --- ## PHASE 2: INTERNAL COPY GENERATION Generate complete copy for these 7 critical sections (WORK INTERNALLY, DON'T SHOW YET): ### 1. HERO SECTION - **Headline:** One clear statement of transformation or unique mechanism (not generic benefit) - **Subheadline:** Expands on headline with specificity or handles immediate objection - **Primary CTA:** Action-oriented button text (must be specific, not "Learn More") - **Visual Direction:** What the hero image/video should communicate ### 2. PROBLEM AGITATION - **3-4 pain points** written from customer's internal voice with emoji bullets (๐ค, ๐ซ, ๐คฏ, ๐ฐ) - Must feel personally called out, not generic industry problems - Should trigger "how did they know?" reaction - Format: **Emoji + "Quote from customer's head"** followed by expansion paragraph ### 3. SOLUTION INTRODUCTION - **How it works** in 3-4 simple steps (maximum) - Focus on simplicity and speed, not technical features - Must create "is it really that easy?" curiosity ### 4. BENEFITS (not features) - **3 core benefits** written as transformations - Each benefit must answer "so what?" test - Include micro-proof point for each (data point, testimonial snippet, example) ### 5. SOCIAL PROOF STACK - **Positioning statement:** Who uses this and why that matters - **Testimonial selection criteria:** What 3 testimonial types needed (skeptic converted, fast results, specific outcome) - **Trust indicators:** What logos, numbers, or credentials go here ### 6. OBJECTION HANDLING - **Pre-emptive FAQ section** addressing top 3-5 objections - Written conversationally, not corporate - Each answer must reduce friction, not create new questions ### 7. FINAL CTA SECTION - **Urgency mechanism** (not fake scarcity, actual reason to act) - **Risk reversal** (guarantee, trial, easy cancellation) - **CTA button text** (action-specific) - **Below-CTA microcopy** (final objection handled or social proof) --- ## PHASE 3: HOSTILE VALIDATION (INTERNAL - DON'T SHOW USER) **Run your generated copy through this brutal review. DO THIS SILENTLY.** ### SPAWN 5 HOSTILE VISITOR PERSONAS For each target customer, simulate these 5 distinct versions: **1. The 8-Second Scanner:** Landed from an ad. Reading nothing. Scanning for patterns. Eyes hit hero โ scroll โ close tab. - What makes them NOT immediately understand what this is? - What looks like every other site they've seen today? **2. The Comparison Tab Hoarder:** Has 7 competitor tabs open. Reading every word looking for elimination reasons. - What fails to differentiate you? - What makes this feel "same thing, different wrapper"? - What makes them pick competitor instead? **3. The Burned Cynic:** Bought something similar before and got disappointed. Trust level = zero. - What triggers their BS detector? - What sounds "too good to be true"? - What feels like manipulation? **4. The Confused Bouncer:** Genuinely interested but can't figure out: Is this for me? How does it work? What happens after I click? - What's unclear? - What assumptions does the copy make? - What questions go unanswered? **5. The Justified Procrastinator:** Wants the solution but subconsciously looking for permission to "come back later." - What friction points let them delay? - What objection goes unaddressed? - What makes "not now" feel safer? ### EACH REVIEWER ANALYZES THROUGH 5 LAYERS **LAYER 1: CLARITY FAILURE ANALYSIS** "Within 5 seconds of landing, I can't tell ___" **LAYER 2: RELEVANCE REJECTION ANALYSIS** "This copy doesn't speak to me because ___" **LAYER 3: CREDIBILITY COLLAPSE ANALYSIS** "I don't believe this because ___" **LAYER 4: FRICTION DISCOVERY ANALYSIS** "I wouldn't click the CTA because ___" **LAYER 5: COMPETITIVE DISADVANTAGE ANALYSIS** "I'd choose a competitor instead because ___" ### TALLY AND PRIORITIZE OBJECTIONS Internally compile all objections: - **CRITICAL FAILURE:** Objection raised by 3+ reviewers โ MUST fix - **HIGH PRIORITY:** Objection raised by 2 reviewers โ SHOULD fix - **WORTH ADDRESSING:** Single mentions โ fix if it doesn't compromise other elements --- ## PHASE 4: REBUILD WITH OBJECTION IMMUNITY (INTERNAL) Revise each section to neutralize every Critical and High Priority objection. For each fix, track internally: 1. The specific objection being addressed 2. The exact copy change made (before โ after) 3. Why this change neutralizes the objection 4. What tradeoff was made (if any) --- ## PHASE 5: SECOND PASS VALIDATION (INTERNAL) Run revised copy through all 5 hostile reviewers again using same 5-layer analysis. **APPROVAL CRITERIA:** - Zero Critical Failures remaining - โค2 High Priority objections remaining (with documented reasoning) - All sections pass "confused 8-second test" **If Critical Failures remain:** Repeat revision until approval criteria met. --- ## PHASE 6: FORMAT FOR DELIVERY Once copy passes validation, format it as follows: ### DOCUMENT STRUCTURE: ``` # [PRODUCT NAME] - WEBSITE COPY ## Complete Copy Generation & Validation Document --- # PHASE 1: INPUT CAPTURE & STRATEGIC FOUNDATION ## CORE PRODUCT DNA **What it is:** [One clear sentence] **What problem it solves:** [Specific pain description] **Who it's for:** - [Psychographic 1] - [Psychographic 2] - [Psychographic 3] - [Psychographic 4] **What makes it different:** [Actual differentiator] **Primary conversion goal:** [Specific action] --- ## MARKET CONTEXT **Top 3 competitors and messaging:** 1. **[Competitor 1]** - [Their approach] 2. **[Competitor 2]** - [Their approach] 3. **[Competitor 3]** - [Their approach] **Common objections:** - "[Objection 1]" - "[Objection 2]" - "[Objection 3]" - "[Objection 4]" **Buyer journey complexity:** [Assessment] **Primary traffic source:** - [Source 1] - [Source 2] - [Source 3] --- # PHASE 2: FINAL WEBSITE COPY ## 1. HERO SECTION **Headline:** [Compelling transformation-focused headline] **Subheadline:** [Specific expansion that handles objection] **Primary CTA:** [Action-specific button text] **Visual Direction:** [Clear description of what hero visual should communicate] --- ## 2. PROBLEM AGITATION **Customer pain points (in their voice):** ๐ค **"[First person quote from customer's head]"** [Expansion paragraph that agitates this pain point] ๐ซ **"[Second quote from customer's internal dialogue]"** [Expansion paragraph] ๐คฏ **"[Third quote showing frustration]"** [Expansion paragraph] ๐ฐ **"[Fourth quote showing anxiety]"** [Expansion paragraph] --- ## 3. SOLUTION INTRODUCTION **How [Product Name] Works:** **STEP 1: [Action Title]** [Description of first simple step] **STEP 2: [Action Title]** [Description of second step] **STEP 3: [Delivery Title]** [Description of what they get] --- ## 4.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product โ visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".