← Back to Skills Marketplace
brianrwagner

Testimonial Collector

by Brian Wagner · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
641
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install brw-testimonial-collector
Description
Systematically gather and format client testimonials. Use when someone needs social proof, wants to collect feedback, or needs to turn happy clients into pub...
README (SKILL.md)

Testimonial Collector

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.


When to Ask

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.


How to Ask (Without Being Weird)

The Direct Ask

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.


The Question Route

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.


The Draft Route

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.


The Deep Dive (For Case Studies)

When you need more than a quote:

  1. What was the situation before we started?
  2. What almost stopped you from moving forward?
  3. What was it like working together?
  4. What changed as a result?
  5. What would you tell someone considering this?

These five questions give you enough for a full case study.


How to Format What You Get

Short Format (Social/Website)

"[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.


Medium Format (Proposals/About Page)

"[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.


Long Format (Case Study Pages)

**What [Name] at [Company] Said:**

"[Full quote with context — the whole story]"

This goes on dedicated case study pages or in downloadable PDFs.


Editing Rules (Stay Ethical)

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.


The Quality Checklist

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.


Where to Use Testimonials

Location Format Purpose
Homepage Short Trust at first glance
Sales pages Medium Overcome objections
Proposals Medium Relevant proof
LinkedIn Short Credibility
Case studies Long Deep proof

Following Up (If They Don't Respond)

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.


Build a Library

Create a simple doc or spreadsheet:

Client Date Quote Format Permission Used 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

Usage Guidance
This skill is coherent and low-risk technically, but before using it: 1) Always get explicit, recorded permission from the client before publishing a quote (keep approvals). 2) Never add or exaggerate claims or outcomes — follow the skill's 'can't' rules and send edits back for approval. 3) Be mindful of personal data and regional privacy rules (e.g., GDPR); redact or avoid publishing sensitive details. 4) If you plan to automate sending messages, confirm you have the client's consent and that automated delivery is appropriate. 5) Keep your testimonial library secure (access control) and track where each quote is used and when permissions expire.
Capability Analysis
Type: OpenClaw Skill Name: brw-testimonial-collector Version: 1.0.0 The OpenClaw skill bundle contains only metadata and a markdown file with instructions. The SKILL.md provides guidance and templates for collecting client testimonials. There is no executable code, shell commands, network calls, file system interactions, or any instructions that could be interpreted as malicious or as an attempt at prompt injection to subvert the agent's intended behavior. The content is purely advisory and aligns with the stated purpose.
Capability Assessment
Purpose & Capability
Name, description, and runtime instructions all focus on composing asks, questions, draft testimonials, formatting guidance, and a simple tracking spreadsheet — nothing requested or instructed is outside the testimonial-collection purpose.
Instruction Scope
SKILL.md is limited to message templates, question sets, formatting rules, follow-up timing, and a suggested tracking sheet. It does not instruct the agent to access system files, environment variables, or external APIs. Note: the instructions give broad discretion to draft and edit testimonials — the doc includes explicit rules against fabricating or exaggerating claims, but the agent/operator must enforce approval/consent before publishing to avoid ethical or legal issues.
Install Mechanism
No install spec and no code files — instruction-only skills write nothing to disk during install. This is the lowest-risk install model and matches the skill's simple, advisory purpose.
Credentials
The skill requests no environment variables, credentials, or config paths, which is proportionate. However, the skill's use case involves collecting and publishing people’s statements and possibly personal data; users should ensure they obtain explicit permission and comply with applicable privacy rules before storing or publishing testimonials.
Persistence & Privilege
Skill flags are default (not always-on, agent-invocable allowed). It does not request persistent privileges or modify other skills or system settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install brw-testimonial-collector
  3. After installation, invoke the skill by name or use /brw-testimonial-collector
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the testimonial-collector skill. - Provides step-by-step guidance on when and how to ask clients for testimonials. - Includes empathetic, customizable request templates (direct ask, question route, draft route). - Offers detailed formatting tips for short, medium, and long testimonial use cases. - Lays out ethical editing guidelines and a testimonial quality checklist. - Suggests testimonial placement across web, proposals, and social. - Encourages follow-up and testimonial tracking with a review system.
Metadata
Slug brw-testimonial-collector
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Testimonial Collector?

Systematically gather and format client testimonials. Use when someone needs social proof, wants to collect feedback, or needs to turn happy clients into pub... It is an AI Agent Skill for Claude Code / OpenClaw, with 641 downloads so far.

How do I install Testimonial Collector?

Run "/install brw-testimonial-collector" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Testimonial Collector free?

Yes, Testimonial Collector is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Testimonial Collector support?

Testimonial Collector is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Testimonial Collector?

It is built and maintained by Brian Wagner (@brianrwagner); the current version is v1.0.0.

💬 Comments