/testimonials
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,"
$ npx -y skills add kostja94/marketing-skills --skill testimonials --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/testimonials
Context preview
The summary Claude sees to decide when to auto-load this skill.
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,"
SKILL.md
testimonials.SKILL.mdname: testimonials-generator
description: 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.
metadata:
version: 1.0.1
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
Read more
name: testimonials-generator description: 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. metadata: version: 1.0.1
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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
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,"
Open skill - /seo-monitoring
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,"
Open skill - /ai-traffic
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
Open skill - /traffic
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
Open skill - /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
Open skill - /community-forum
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,"
Open skill

