Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Systematically gather and format client testimonials. Use when someone needs social proof, wants to collect feedback, or needs to turn happy clients into pub...
Systematically gather and format client testimonials. Use when someone needs social proof, wants to collect feedback, or needs to turn happy clients into pub...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Here's the reality: your happiest clients will vouch for you. They want to help. But they're busy. And you feel weird asking. So you don't. Meanwhile, you're in sales calls with no social proof, trying to convince people you're good at what you do. This skill fixes the asking part. I'll give you exactly what to say, when to say it, and how to format what you get back.
Timing is everything. These are your windows: โ Right after a win. They just saw results? Ask now. โ When they thank you unprompted. That's your cue. โ At project completion. Natural checkpoint. โ When they renew or extend. They're voting with their wallet. The moment of peak happiness is the moment to ask. Don't wait.
Subject: Quick favor (30 seconds) Hey [Name], Loved working on [project] with you โ especially seeing [specific result you noticed]. Would you be open to sharing a quick testimonial I could use on my site? No pressure. If yes, I can either: A) Send you 3 questions to answer B) Write a draft for you to approve/edit Whatever's easier. Thanks either way. Short. Gives them options. Doesn't make it a big deal.
If they say "sure, what do you need?" โ send this: Awesome. Just 3 quick questions: 1. What was the situation before we worked together? 2. What changed or improved? 3. Would you recommend this to others? Why? A few sentences each is perfect. I'll format it. That's it. Don't overthink it.
Some people hate writing. Make it easy: I drafted something based on our work together: "[Your draft in their voice โ keep it short and specific]" Feel free to edit, tweak, or rewrite entirely. Whatever feels right to you. Most people will approve with minor edits. You did the hard part.
When you need more than a quote: What was the situation before we started? What almost stopped you from moving forward? What was it like working together? What changed as a result? What would you tell someone considering this? These five questions give you enough for a full case study.
"[One punchy sentence about the result]" โ [Name], [Title] at [Company] Example: "Brian helped us go from zero LinkedIn presence to 3 inbound leads per week in 6 weeks." โ Sarah Chen, CEO at TechCo This goes on your homepage, your proposals, your LinkedIn featured section.
"[2-3 sentences: problem, experience, result]" โ [Name], [Title] at [Company] Example: "We knew we needed to build our founder brand but had no idea where to start. Brian built us a complete content system in 6 weeks โ now we're generating inbound leads for the first time. Can't recommend him enough." โ Sarah Chen, CEO at TechCo This goes in proposals, on your services page, in case studies.
**What [Name] at [Company] Said:** "[Full quote with context โ the whole story]" This goes on dedicated case study pages or in downloadable PDFs.
You can: Fix grammar and typos Tighten for clarity Reorder sentences Cut filler You can't: Add claims they didn't make Exaggerate results Change the meaning Always send edits back for approval. Takes 30 seconds and keeps you honest.
Strong testimonials have: Specific result โ Numbers or concrete outcomes Before/after โ What changed Credibility markers โ Name, title, company Relevance โ Similar to your ideal client Weak: "Great to work with!" Strong: "Went from 0 to 3 inbound leads per week in 6 weeks." Specificity is what makes people believe it.
LocationFormatPurposeHomepageShortTrust at first glanceSales pagesMediumOvercome objectionsProposalsMediumRelevant proofLinkedInShortCredibilityCase studiesLongDeep proof
Wait 5-7 days. Send one follow-up: Hey [Name], just bumping this โ no pressure at all. If timing's bad, totally get it. Let me know either way! If they don't respond to that, let it go. Some people just won't, and that's fine.
Create a simple doc or spreadsheet: ClientDateQuoteFormatPermissionUsed Where Review it quarterly: Who haven't you asked? Which testimonials are getting stale? Any gaps in industries or use cases? Need help building your social proof library? โ Book a strategy call Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.