kostja94/customer-stories-page-generator
skills/pages/marketing/customer-stories/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add kostja94/marketing-skills customer-stories-page-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 6:44 PM119.3s1 file scanned
SKILL.md
- 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.
- 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
kostja94/xml-sitemap
testing
VerifiedTrustedCommunity
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
588SKILL.mdUpdated Apr 24, 2026
kostja94/robots-txt
development
VerifiedTrustedCommunity
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
588SKILL.mdUpdated Apr 24, 2026
kostja94/programmatic-seo
testing
VerifiedTrustedCommunity
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
588SKILL.mdUpdated Apr 24, 2026
kostja94/twitter-cards
data-ai
VerifiedTrustedCommunity
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
571SKILL.mdUpdated Apr 24, 2026