skillboardUpdated every 6 hours
skillboardWhen 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.
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.
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:
| 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) |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/customer-stories · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/customer-stories"
cp -r "skills/pages/marketing/customer-stories" ".claude/skills/customer-stories"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.