customer-stories-page-generator
This skill guides the creation and optimization of customer story and case study pages by structuring content around the challenge-solution-results framework, identifying relevant industries and metrics, and applying best practices for conversion. Use it when developing full case studies, testimonials pages, success stories, or social proof content to build credibility and shorten sales cycles through quantifiable customer results.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/customer-stories-page-generator && cp -r /tmp/customer-stories-page-generator/skills/pages/marketing/customer-stories ~/.claude/skills/customer-stories-page-generatorSKILL.md
# Pages: Customer Stories Guides customer story and case study page content, structure, and conversion. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, proof points, and customer language. Identify: 1. **Story format**: Full case study, quote snippet, video 2. **Industries/use cases**: Who to showcase 3. **Metrics**: What results to highlight ## Best Practices ### Structure (Challenge -> Solution -> Results) | Section | Content | |---------|---------| | **Headline** | Benefit-driven; lead with outcome | | **Challenge** | Client's problem, pain points | | **Solution** | How your product helped | | **Results** | Quantifiable metrics, before/after | | **Quote** | Direct testimonial from client | | **CTA** | Next step (demo, contact, read more) | ### Content Principles - **Lead with results**: Outcomes first, not background - **Specific metrics**: "Increased revenue 40%" not "great results" - **Quotes**: Direct, attributed, credible - **Scannable**: Consistent template; easy to skim - **Concise**: Enough value without losing interest ### Visual Elements - **Logos**: Client branding (with permission) - **Charts/graphs**: Before-after, metrics - **Video**: Testimonials, interviews - **Expandable sections**: For deeper detail ### Why It Matters - 54% of buyers review case studies before purchasing - 73% of successful content marketers use them - Builds credibility, justifies pricing, shortens sales cycles ### Storytelling - **Problem** = beginning - **Solution** = climax - **Results** = resolution - **Hard facts**: Statistics for impact ## Output Format - **Template** structure - **Story** outline (challenge, solution, results) - **Metrics** to capture - **SEO** metadata and schema (if indexing) - **Internal linking** to product/pricing ## Related Skills - **landing-page-generator**: Case studies and testimonials for LP social proof (step 2) - **url-slug-generator**: URL slug for case study pages (e.g. /customers/case-slug); 3-5 words - **about-page-generator**: Social proof complements About - **pricing-page-generator**: Case studies support pricing justification - **homepage-generator**: Customer stories on homepage - **schema-markup**: CaseStudy schema
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.