Ask happy clients for a testimonial or review the right way — timed well, easy to give, and specific enough to actually persuade future clients. Use when asked to get testimonials, ask for a review, how to request a testimonial, or get social proof from clients. Produces the right moment and channel to ask, a message that makes saying yes effortless, guiding questions that yield specific results-based testimonials (not 'great to work with'), how to handle a written vs video ask, and permissio...
Scanned 9/3/2026
Install to Claude Code
npx -y skills add mohitagw15856/pm-claude-skills --skill testimonial-request --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Testimonial Request?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mohitagw15856-testimonial-request)More formats (shields.io, HTML) on the badges page.
---
name: testimonial-request
description: "Ask happy clients for a testimonial or review the right way — timed well, easy to give, and specific enough to actually persuade future clients. Use when asked to get testimonials, ask for a review, how to request a testimonial, or get social proof from clients. Produces the right moment and channel to ask, a message that makes saying yes effortless, guiding questions that yield specific results-based testimonials (not 'great to work with'), how to handle a written vs video ask, and permission/usage basics — without being pushy or fishing for praise."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/testimonial-request.html
metadata:
{
"openclaw": { "emoji": "🧠" }
}
---
# Testimonial Request
Testimonials are the highest-converting marketing you have, and most freelancers/businesses never collect them — or collect vague "they were great!" ones that persuade no one. The fix is asking at the right moment, making it effortless, and guiding the client toward a specific, results-focused answer. This does that without feeling like you're fishing for compliments.
## What This Skill Produces
- **The right moment & channel** — when to ask (right after a win/result) and how (email, call, form)
- **An effortless ask** — a message that makes giving a testimonial quick and low-effort, including an offer to draft or prompt
- **Guiding questions** — prompts that yield specific, results-based testimonials ("cut our onboarding time in half") instead of generic praise
- **Written vs. video** — how to ask for each, and when video is worth it
- **Permission & usage** — getting the OK to use it, with name/role/company, and where you'll feature it
- **A graceful tone** — confident and appreciative, not needy or pushy
## Required Inputs
Ask for these if not provided:
- **The client & result** — who, and the concrete outcome you delivered
- **The relationship** — how warm, and how the project ended
- **What you want** — a written quote, a review on a platform, a video, or a case study
- **Where it'll be used** — website, proposals, a specific review site
- **Timing** — just wrapped, or an older happy client
## Framework: Right Time, Easy Yes, Specific Answer
1. **Ask at peak goodwill.** Right after a delivered result or a moment of client delight is when a yes (and enthusiasm) is highest.
2. **Make it effortless.** Busy clients skip open-ended asks — offer a couple of guiding questions, or even a draft they can edit, and keep it a 2-minute favor.
3. **Guide toward specifics.** Prompt for the concrete before/after and results; a specific outcome persuades future clients far more than "highly recommend."
4. **Match the format to the value.** Written is easy and flexible; video converts harder but asks more — choose deliberately and make the video ask especially low-effort.
5. **Get clear permission.** Confirm you can use it with their name/role/company and where — a testimonial you can't attribute is weaker.
6. **Stay gracious.** Confident and appreciative; one polite follow-up if needed, never nagging.
## Output Format
### Testimonial request: [client] · result [x] · want [written/review/video]
**When/where to ask:** [peak-goodwill moment · channel].
**The message**
> [Warm, specific to the result, effortless ask + guiding questions or an offer to draft, and where it'll help].
**Guiding questions (for specifics):** ["what was the problem before?" · "what changed / what result?" · "what would you tell someone considering me?"].
**Format note:** [written vs video — the ask + effort].
**Permission:** [OK to use with name/role/company on [placement]].
**Tone:** appreciative, not needy; one gentle follow-up max.
## Quality Checks
- [ ] Times the ask to peak client goodwill
- [ ] Makes giving it effortless (prompts or a draft offer)
- [ ] Guides toward specific, results-based content
- [ ] Chooses written vs video deliberately
- [ ] Secures usage permission with attribution
- [ ] Tone is gracious, not pushy or praise-fishing
## Anti-Patterns
- **Asking too late** when the goodwill has faded.
- **An open-ended ask** that yields "great to work with!"
- **No guiding questions** — vague, unpersuasive quotes.
- **Making it high-effort** for a busy client.
- **Using it without permission/attribution.**
- **Nagging** for it.
## Example Trigger Phrases
- "How do I ask a client for a testimonial?"
- "Write a message requesting a review from a happy customer."
- "Get me a specific testimonial, not just 'they were great'."
- "Should I ask for a written or video testimonial, and how?"
- "How do I request a case-study quote after finishing a project?"
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!