When the user wants to add, optimize, or design customer testimonials, reviews, or case study sections. Also use when the user mentions "testimonials," "reviews," "customer quotes," "social proof," "case studies," "testimonial section," "customer reviews," "review schema," "testimonial design," or "social proof section." For case studies page, use customer-stories-page-generator.
Guides testimonial design and placement for conversion. 92% of consumers read reviews before buying; testimonials can increase conversion by up to 67%.
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 customer personas and industries.
Identify:
| Format | Effectiveness | Best For | |--------|---------------|----------| | Video | Highest; 77% say it influences buying | Key landing pages | | Text + photo | Versatile; easy to implement | Product, pricing | | Case study | Deep credibility; specific outcomes | B2B, high-value | | Star ratings | Quick trust signal | E-commerce |
Video: 95% message retention vs 10% for text.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/testimonials · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/testimonials"
cp -r "skills/components/conversion/testimonials" ".claude/skills/testimonials"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.