testimonials-generator
# Testimonials-Generator The testimonials-generator skill helps users design and optimize customer testimonials, reviews, and social proof sections to increase conversion rates. Use this skill when requesting assistance with testimonial placement, format selection, content strategy, credibility signals, or accessibility for reviews and customer quotes on websites or landing pages.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/testimonials-generator && cp -r /tmp/testimonials-generator/skills/components/conversion/testimonials ~/.claude/skills/testimonials-generatorSKILL.md
# Components: Testimonials 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. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for customer personas and industries. Identify: 1. **Content type**: Text quotes, video, case studies 2. **Placement**: Product pages, pricing, hero, dedicated page 3. **Audience**: B2B vs B2C; industry/role relevance ## Content Formats | 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. ## Best Practices ### Content - **Specific results**: "Increased revenue by 40%" over generic praise - **Real photos and names**; avoid stock images - **Variety**: Different customer types, industries, use cases - **Current**: Update regularly; remove outdated testimonials ### Placement - Product pages, pricing sections, near CTAs - Filter by industry/role so prospects see relevant stories - Organize by integration or outcome for specificity ### Credibility Signals - Company logos, job titles - Verified reviews (badges, links) - Links to customer profiles or live stores when possible - Before/after narratives for emotional connection ## Design Guidelines - Clean layouts; readable typography - Engaging visuals; avoid clutter - Mobile-optimized; fast loading - Carousel for multiple testimonials; see **carousel** for design and accessibility ## SEO - Testimonial content can include keywords naturally - Structured data (Review, AggregateRating) for rich snippets ## Accessibility - Provide alt text for photos - For carousel design and accessibility (keyboard nav, user control), see **carousel** ## Output Format - **Format recommendations** (text, video, case study) - **Placement** suggestions - **Content** guidelines (specificity, credibility) - **Design** checklist ## Related Skills - **carousel**: Carousel layout for multiple testimonials; design and accessibility - **landing-page-generator**: Testimonials as step 2 (earn trust) in landing page flow - **trust-badges-generator**: Complementary trust signals; logos and badges - **hero-generator**: Testimonials in hero for social proof - **cta-generator**: Place testimonials near CTAs; boost conversion - **pricing-page-generator**: Testimonials on pricing pages
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
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 track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
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 setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.