/customer-stories
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
$ npx -y skills add kostja94/marketing-skills --skill customer-stories --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/customer-stories
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
customer-stories.SKILL.mdname: 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: 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
Read more
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: 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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
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
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
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
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill

