customer-stories-page-generator
kostja94/marketing-skills
How to install customer-stories-page-generator
npx skills add https://github.com/kostja94/marketing-skills --skill customer-stories-page-generatorFull instructions (SKILL.md)
Source of truth, from kostja94/marketing-skills.
name: customer-stories-page-generator description: When the user wants to create, optimize, or audit customer stories or case study pages. Also use when the user mentions "case studies," "customer stories," "success stories," "testimonials page," "case study," "customer proof," "social proof page," or "results page." For testimonial components, use testimonials-generator. metadata: version: 1.0.1
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:
- Story format: Full case study, quote snippet, video
- Industries/use cases: Who to showcase
- 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
Related skills
More from kostja94/marketing-skills and the wider catalog.
directory-listing-ads
When the user wants to run paid ads within directories or marketplaces. Also use when the user mentions "Taaft ads," "Shopify App Store ads," "G2 sponsored," "Capterra ads," "directory ads," "marketplace ads," "paid listing," "sponsored listing," or "directory promotion." For organic listings, use directory-submission.
directory-submission
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
discount-marketing-strategy
When the user wants to plan, implement, or optimize discount and promotional pricing strategy. Also use when the user mentions "discount strategy," "promo code," "coupon," "redeem code," "lifetime deal," "LTD," "AppSumo," "Black Friday," "Cyber Monday," "BFCM," "seasonal sale," or "promotional pricing." For pricing page, use pricing-page-generator.
display-ads
When the user wants to run display, banner, or ad network campaigns. Also use when the user mentions "display ads," "banner ads," "ad network," "ad alliance," "programmatic display," "native ads," or "retargeting display." For strategy, use paid-ads-strategy.
distribution-channels
When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.