testimonial-collector

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: testimonial-collector
description: Systematically gather, score, and format client testimonials. Use when someone needs social proof, wants to collect feedback, needs to turn happy clients into public advocates, or asks for help requesting or drafting a testimonial.
---

# Testimonial Collector

## Mode

Detect from context or ask: *"One script, full system, or full system with campaign?"*

| Mode | What you get | Best for |
|------|-------------|----------|
| `quick` | 1 outreach script + 1 format template | Asking one client, right now |
| `standard` | Full collection system: timing, scripts, formatting, display guidance | Building repeatable social proof |
| `deep` | Full system + multi-channel strategy + case study pipeline | Sales enablement, proposal library |

**Default: `standard`** — use `quick` if they have one client in mind. Use `deep` if they want a system they can hand to a VA.

---

## Context Loading Gates

**Before proceeding, gather:**
- [ ] Client name, company, and industry
- [ ] Project type and specific deliverables
- [ ] Key results — push for at least one number ("even a rough estimate")
- [ ] Desired output format (short quote / medium paragraph / full narrative)
- [ ] Urgency (this week vs. building a library)

If results are vague (e.g., "things improved"), **stop and ask:** "Can you name one specific number — even a rough estimate? That's what makes a testimonial credible and usable." Do not draft until you have this.

If the user wants to skip a field: note it and flag the quality impact in the output.

---

## Phase 1: Situation Analysis

Before drafting anything, reason through:

1. **Client relationship stage:** Was this a quick project or a deep engagement? Depth affects how much authentic language is available.
2. **Results clarity:** Are the outcomes measurable (numbers, timelines, named outcomes) or soft (vibes, general satisfaction)?
3. **Format match:** What placement does the user need this for? A homepage needs different length than a sales deck.
4. **Voice data:** Does the user have existing communication from this client (emails, Slack, quotes) that can inform tone?

Output a brief situation summary:
> "You have a [length] engagement with [client] in [industry], with [strong/weak] results data. I'll draft in [format] with [authentic/templated] voice. Main gap to address: [specific gap]."

---

## Phase 2: Quality Scoring Framework

Score the raw testimonial content (or anticipated content) before drafting:

| Dimension | Score 1 | Score 3 | Score 5 |
|---|---|---|---|
| **Specificity** | No details | Vague references | Specific named result |
| **Measurability** | "It was great" | "Noticeable improvement" | "40% increase in leads" |
| **Authentic Voice** | Sounds like ad copy | Slightly stilted | Reads exactly how a person talks |
| **Length** | Too short (no context) | Decent but thin | Enough for all 3 formats |

**Scoring rule:**
- 4+ on all 4 dimensions → ready to use
- ≤2 on any dimension → apply iteration protocol before delivering

---

## Phase 3: Draft Generation

### The Ask Templates

**Direct Ask:**
```
Subject: Quick favor (30 seconds)

Hey [Name],

Loved working on [project] with you — especially seeing [specific result].

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.
```

**Question Route:**
```
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?
```

**Draft-on-Behalf Framework:**
Rules for writing in the client's voice:
- **Tone:** Match their actual communication style (check emails/messages for vocabulary)
- **Structure:** Situation Before → What Changed → Specific Result → Recommendation
- **Avoid:** Superlatives without evidence ("amazing," "life-changing")
- **Avoid:** Leading with praise — lead with the cli