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 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," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
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," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 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 analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-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 setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
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," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.