Testimonial Request Writer

What it does

Given some context on why a customer seems happy, a positive support interaction, a completed milestone, a direct compliment, writes a brief, personal request asking for a testimonial that references that specific context rather than a generic review blast. Suggests one or two easy ways to give it, a short reply, a review link, a quick call, so the ask has low friction.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/testimonial-request-writer/ (or ~/.claude/skills/testimonial-request-writer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/testimonial-request-writer/

OpenAI Codex

.codex/skills/testimonial-request-writer/

Cursor

.cursor/skills/testimonial-request-writer/ (or ~/.cursor/skills/testimonial-request-writer/ globally)

Compatibility

Any WordPress site; works well paired with a reviews or testimonials plugin, but the request itself can go out over any email tool.

The complete SKILL.md for this skill:

---
name: testimonial-request-writer
description: Use when a user wants a testimonial or review request drafted for a happy customer, or asks to "ask for a testimonial" or "request a review".
---

# Testimonial Request Writer

## When to use
A customer has recently shown they're happy, through a compliment, a milestone, or a good support interaction, and the user wants to ask them for a testimonial while it's still fresh.

## Procedure
1. Read the context for why this customer seems like a good candidate, a positive support ticket, a compliment they sent, or reaching a usage milestone.
2. Draft a short, specific request that references that actual moment, not a generic feedback opener.
3. Ask one clear question or offer one easy path to respond, replying to the email or a short review form link, rather than an open-ended prompt.
4. Keep the message short enough to read in 10 seconds, since this is a favor being asked, not a survey.
5. Add a genuine thank-you regardless of whether they choose to respond, no guilt-driven language.

## Guardrails
- Don't reference private support details in a way that could feel surveillance-like, keep the reference to what the customer themselves said or did.
- Never fabricate a compliment or interaction as the pretext if none was actually given.