New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prd V10 Testimonial Collector

by mattgierhart in mattgierhart/PRD-driven-context-engineering

Systematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption.

MITAuto-check passedProduct & Project Management

Install Prd V10 Testimonial Collector

skills CLI
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-testimonial-collector -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-testimonial-collector --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-v10-testimonial-collector .claude/skills/prd-v10-testimonial-collector && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prd-v10-testimonial-collector
GitHub stars
180
Token cost
~2.8k tokens
SKILL.md length
1,045 words
Files
1
Skills in repo
45
Repo updated
First seen
Licence
MIT

At a glance

Systematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption.

  • Works in 5 steps: Identify collection triggers — Each… → Build per-trigger collection mechanism → Process incoming testimonials — Each… → …
  • Requests to collect testimonials
  • SKILL.md covers Execution Mode, What This Does, How It Works and Example, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prd V10 Testimonial Collector is an agent skill from mattgierhart/PRD-driven-context-engineering. Systematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption. Triggers on requests to collect testimonials, set up social proof harvest, gather customer quotes, or when user asks "how do we get testimonials?", "social proof harvest", "NPS responses", "testimonial wall", "customer quotes", "post-purchase survey", "milestone follow-up". Outputs CFD-TST- testimonial entries and GTM-TST- placement assets.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing, Project management and Customer feedback analysis. The repository describes itself as: PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD… The licence is MIT.

When your agent uses it

  • Requests to collect testimonials
  • Set up social proof harvest
  • Gather customer quotes
  • User asks how do we get testimonials?

Example prompts

  • “how do we get testimonials?”
  • “social proof harvest”
  • “NPS responses”
  • “/prd-v10-testimonial-collector”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify collection triggers — Each trigger is an event that suggests the customer is in a moment to share positive feedback
  2. Build per-trigger collection mechanism
  3. Process incoming testimonials — Each goes through
  4. Place in marketing surfaces — Per testimonial
  5. Measure placement performance [standard+] — Some testimonials convert; some don't. Track per-placement conversion to identify which quotes…

What it can do on your machine

Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd V10 Testimonial Collector loads about 2.8k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 1,045 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 1,045 words, ~2,767 tokens.

Download SKILL.mdSave it as .claude/skills/prd-v10-testimonial-collector/SKILL.md (or your agent's skills folder).
name
prd-v10-testimonial-collector
description
Systematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption. Triggers on requests to collect testimonials, set up social proof harvest, gather customer quotes, or when user asks "how do we get testimonials?", "social proof harvest", "NPS responses", "testimonial wall", "customer quotes", "post-purchase survey", "milestone follow-up". Outputs CFD-TST-* testimonial entries and GTM-TST-* placement assets.
allowed-tools
Read, Write, Edit, Glob, Grep
context
fork
execution_modes.default
standard
execution_modes.supports
quick, standard, deep

Testimonial Collector

Position in workflow: v1.0 Case Study Builder → v1.0 Testimonial Collector → GTM channels (placement)

Execution Mode

Default is standard. See .claude/rules/08-skill-execution-modes.md for selection logic.

ModeWhat this skill produces
quickOne trigger (e.g., NPS promoters) + collection email + 5–10 testimonials processed
standard3 triggers (NPS, milestone, post-purchase) + processing workflow + consent management + per-placement formatting
deep5+ triggers + automated harvest + sentiment-segmentation + per-segment placement targeting + measurement loop

What This Does

Systematically harvests short-form testimonials — 1–3 sentence quotes with name + role + logo — and processes them into placement-ready assets. Testimonials are the lower-effort complement to case studies: they don't carry a full story but they multiply social proof on landing pages, pricing pages, ad creative, and outreach.

This skill solves the "we have happy customers but no quotes" problem — most teams have plenty of positive feedback in support tickets, NPS responses, and renewal calls, but never capture it as marketing-ready assets. The fix is a system, not heroic effort.

How It Works

  1. Identify collection triggers — Each trigger is an event that suggests the customer is in a moment to share positive feedback:
    • NPS Promoter response (score 9–10) — Lowest-friction; they already wrote feedback
    • Activation milestone (Day 30 / Day 90 active) — They've seen value by now
    • Post-purchase / post-upgrade — Decision fresh in mind
    • Renewal — Strong signal of ongoing value
    • Support resolution (positive) — Acute "you saved my day" moment
    • Referral from customer — They already advocated
  2. Build per-trigger collection mechanism:
    • NPS Promoter → automated email asking permission to use response + adding 1-question follow-up
    • Milestone → in-app prompt or email with one-line ask
    • Post-purchase → email 7 days after purchase
    • Renewal → CSM-led ask during renewal call
    • Support → followup in support thread after positive resolution
  3. Process incoming testimonials — Each goes through:
    • Consent confirmation (scope: name? role? logo? use anywhere?)
    • Light edit for clarity (their voice; don't rewrite)
    • Tag by segment fit (in-beachhead / adjacent / off-segment)
    • Tag by outcome theme (speed / cost / activation / quality / etc.)
  4. Place in marketing surfaces — Per testimonial:
    • Pricing page (logo + quote)
    • Landing page hero (1 prominent quote)
    • Feature pages (segment-relevant quotes)
    • Ad creative (testimonial-style ads)
    • Email signatures / sales decks
    • Investor decks
  5. Measure placement performance [standard+] — Some testimonials convert; some don't. Track per-placement conversion to identify which quotes earn their spot.

Example

B2B SaaS, 3 collection triggers active.

Trigger 1: NPS Promoter (9–10). NPS run quarterly. Promoters get followup email:

Thanks for the 10! Your response — "Cut our reporting time in half" — would be a powerful testimonial for our pricing page. May we use it with your name and role? Reply YES and we'll send back the version we'd publish for your approval.

Auto-fires when NPS response submitted with score ≥ 9.

Trigger 2: Day-30 active milestone. In-app prompt at first login after Day 30 active:

You've been active for a month! In one sentence, what's working best? → [text box] → [Submit + permission checkbox]

Trigger 3: Post-purchase (Day 7). Email 7 days after first paid charge:

Quick favor — what convinced you to upgrade? Your answer might appear (with your permission) on our pricing page.

Processing: Inbound testimonials enter a triage doc. Per testimonial:

  • Consent confirmed (scope: name / role / logo / anywhere)
  • Light edit (clarity only — kept their voice)
  • Segment tag (in-beachhead: yes/no)
  • Theme tag (speed / cost / activation / quality)
  • Placement decision (pricing / landing / feature page / ad / multi)

Placement: Pricing page logo wall expanded with 6 new testimonials in the beachhead segment. A/B test the hero-section quote on landing pages.

What You Get Back

  • CFD-TST-* entries — One per testimonial; the durable record with consent, source, segment, theme
  • GTM-TST-* entries — Per-placement formatting (the placed quote with surrounding context)
  • Consent records — Customer-by-customer scope and version history
  • Placement-performance log — Per-quote conversion rate (which testimonials earn their spot)

When to Use It

TriggerMode
First testimonial harvest system (none in place)standard
Quarterly NPS run + harvestquick
Pricing page redesign needs more social proofstandard
Landing page A/B test needs quote variantsquick
Pre-investor / pre-Series A push for logo + quote densitydeep
New segment expansion (need segment-specific testimonials)deep
Show full SKILL.md (394 more words)Show less

Consumes

  • CFD-* customer feedback (all sources, especially v0.9 feedback loop) — Raw inbound testimonial material
  • NPS / CSAT data (from v0.9 Feedback Loop Setup) — Promoter responses are the highest-yield source
  • ADO-REF-* candidates — Reference accounts already in cultivation are testimonial-eligible
  • PER-* personas + ADO-BEACHHEAD-* — Segment tagging
  • BR-POS-* — Tone constraints; testimonials shouldn't contradict positioning

Produces

  • CFD-TST-* entries in SoT/SoT.customer_feedback.md
  • GTM-TST-* entries (with Type=Testimonial-Placement) per placement
  • Consent records — Append-only log with scope and version
  • Placement-performance metrics — Per-quote A/B data feeding back into selection

Output Template

CFD-TST-XXX: Testimonial — [Customer name]
Type: Testimonial
Date received: YYYY-MM-DD
Source trigger: [NPS-promoter | Day-30-milestone | Post-purchase | Renewal | Support | Referral]
Customer: [Name, Role, Company, Logo]

Verbatim text:
  "[The actual quote, lightly edited for clarity only]"

Original text (for audit):
  "[The raw response]"

Tags:
  Segment fit: [In-beachhead | Adjacent | Off-segment]
  Theme: [Speed | Cost | Activation | Quality | Reliability | Specific-use-case]
  Length: [Words / chars]

Consent:
  Scope: [Name? Role? Logo? Use-anywhere?]
  Approved by: [Customer name]
  Approved date: YYYY-MM-DD
  Approved version: vX

Placement eligibility:
  - Pricing page logo wall: [Yes/No]
  - Landing page hero: [Yes/No]
  - Feature page (which): [Yes/No]
  - Ad creative: [Yes/No]
  - Sales deck: [Yes/No]
  - Investor deck: [Yes/No]

Linked IDs: PER-XXX (segment), ADO-REF-YYY (if cultivated), CFD-ZZZ (interview source if applicable)
GTM-TST-XXX: Testimonial Placement — [Quote summary]
Type: Testimonial-Placement
Source: CFD-TST-AAA
Placement: [URL or surface, e.g., "/pricing — hero zone"]
Format: [Quote + Name + Role + Logo | Quote + Logo only | Quote in card]

Surrounding context:
  [What this testimonial sits next to — headline, CTA, product feature]

A/B test (if active):
  Variant A: [This testimonial]
  Variant B: [Alternative]
  Metric: [Click-through, signup-rate, etc.]
  Started: YYYY-MM-DD

Performance (if measured):
  [Per-quote conversion data]

Linked IDs: CFD-TST-AAA (source), GTM-YYY (page channel), KPI-ZZZ (placement metric)

Anti-Patterns

PatternSignalFix
Heroic one-time harvest"We collected 20 testimonials in a sprint, then stopped"Triggers run continuously; harvest is a system, not a project
No consent recordPublishing without explicit approvalConsent record per testimonial, scope-explicit
Marketing rewrite"I love [product]" rewritten from "It's pretty useful"Light edits for clarity only; their voice
No segment taggingAll testimonials placed everywhereSegment-relevant placement converts better; tag and target
Stale wallsPricing page testimonials from 2 years agoRefresh quarterly; rotate underperformers
No placement measurementAll testimonials treated as equally goodSome quotes convert 3× others; measure and prune
Anonymous testimonials"VP at major fintech" with no name/logoPragmatists discount anonymous; named + logo or skip
Off-segment testimonials during chasm crossingVisionary-startup quotes on a page targeting enterprise pragmatistsIn-segment placements only during chasm crossing

Quality Gates

Before placing testimonials:

  • Consent on record (scope explicit)
  • Customer name + role + logo (or rationale for less)
  • Segment tag applied
  • Theme tag applied
  • Light edit only (their voice preserved)
  • Placement matches segment fit (in-beachhead testimonials for pragmatist surfaces)
  • BR-POS-* constraints honored (no contradiction with positioning)
  • Refresh cadence committed (quarterly minimum)

Downstream Connections

ConsumerWhat it usesExample
Launch Channels (ORB)Testimonials are Owned-channel content + Borrowed-channel ad creativePricing-page testimonials = Owned; testimonial-style ads = Paid-Borrowed
Alternatives Pages"Pick us if..." sections feature segment-relevant testimonialsMigration-from-X testimonial anchors the alt page
Case Study BuilderStrong testimonials surface case-study candidatesRepeat testimonialer with strong outcome → case study
Cold Outreach (Tiered)Testimonials cited in Touch 2/3 of sequencesTier 2 email includes in-segment testimonial
Feedback Loop SetupTestimonial sources tie back to feedback channelsNPS promoters feed both feedback and testimonial flow
Investor / Sales decksLogo wall + theme-curated testimonials"Customers in segment X say..."

Detailed References

  • BrianRWagner's testimonial-collector skill (ai-marketing-claude-code-skills)
  • Sean D'Souza, The Brain Audit (using testimonials to overcome buying objections)
  • Joanna Wiebe, Copy Hackers — testimonial-driven landing pages
  • (No bundled references/ — testimonials are the artifact)

© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/prd-v10-testimonial-collector of mattgierhart/PRD-driven-context-engineering.

Open the folder on GitHubat commit 30ed1b0

Compare with similar skills

Prd V10 Testimonial Collector next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prd V10 Testimonial Collector compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd V10 Testimonial Collector this skillmattgierhart/PRD-driven-context-engineering180—~2.8kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
PlaidBuildGreatProducts/plaid218—~1.6kAutomated safety check: PassMIT
Project Planneradrianpuiu/claude-skills-marketplace1001 repos~6kAutomated safety check: PassNone
Shep Workstreamsshep-ai/shep264—~2.5kAutomated safety check: PassMIT
Product Manager SkillsDigidai/product-manager-skills185—~6.1kAutomated safety check: PassCC-BY-NC-4.0

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Plaid

    BuildGreatProducts/plaid

    Product Led AI Development — guides founders from idea to launched product.

    218 GitHub stars~1.6k tokensUpdated 5 mo ago
    Product & Project ManagementAuto-check passed

  • Project Planner

    adrianpuiu/claude-skills-marketplace

    Comprehensive project planning and documentation generator for software projects.

    100 GitHub starsUsed in 1 repo~6k tokens
    Product & Project ManagementAuto-check passed

  • Shep Workstreams

    shep-ai/shep

    A skill your agent uses when a large body of work (a version milestone, an epic, a roadmap, a set of PRDs/design docs) needs to be broken into parallel workstreams and executed with the shep CLI.

    264 GitHub stars~2.5k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Product Manager Skills

    Digidai/product-manager-skills

    PM skill for Claude Code, Codex, Cursor, and Windsurf. An agent skill from Digidai/product-manager-skills.

    185 GitHub stars~6.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • App Spec Packager

    instructa/agent-skills

    A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…

    139 GitHub stars~1.5k tokensUpdated 12 days ago
    Product & Project ManagementAuto-check passed

More from mattgierhart/PRD-driven-context-engineering

All 45 skills in this repo

  • Ghm Gate Check

    mattgierhart/PRD-driven-context-engineering

    Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py).

    180 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes

  • Ghm Harvest

    mattgierhart/PRD-driven-context-engineering

    Extracts durable insights from temp/ files to SoT during EPIC Phase E.

    180 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Ghm Id Register

    mattgierhart/PRD-driven-context-engineering

    Validates and registers new SoT IDs with cross-reference integrity.

    180 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Ghm Sot Builder

    mattgierhart/PRD-driven-context-engineering

    Creates new Source of Truth (SoT) files when existing templates don't fit your needs.

    180 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

  • Prd V01 Problem Framing

    mattgierhart/PRD-driven-context-engineering

    Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark.

    180 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Prd V01 User Value Articulation

    mattgierhart/PRD-driven-context-engineering

    Transform validated pain points into articulated user value statements for PRD v0.1 Spark.

    180 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Prd V10 Testimonial Collector

What does Prd V10 Testimonial Collector do?

Systematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption. Prd V10 Testimonial Collector is an agent skill from mattgierhart/PRD-driven-context-engineering.0 Market Adoption.

When should I use Prd V10 Testimonial Collector?

Prd V10 Testimonial Collector fits situations like: requests to collect testimonials; set up social proof harvest; gather customer quotes; user asks how do we get testimonials?.

How do I install Prd V10 Testimonial Collector in Claude Code?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-testimonial-collector -a claude-code`. Or copy the skill folder (.claude/skills/prd-v10-testimonial-collector in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v10-testimonial-collector in your project. Claude Code loads it when a task matches its description.

How do I install Prd V10 Testimonial Collector in Codex?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-testimonial-collector -a codex`. Or copy the skill folder (.claude/skills/prd-v10-testimonial-collector in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v10-testimonial-collector in your project. Codex loads it when a task matches its description.

Can I use Prd V10 Testimonial Collector in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-testimonial-collector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-v10-testimonial-collector, .gemini/skills/prd-v10-testimonial-collector, .github/skills/prd-v10-testimonial-collector and .opencode/skills/prd-v10-testimonial-collector in your project.

What does Prd V10 Testimonial Collector need to run?

SKILL.md names no scripts, command-line tools or credentials: Prd V10 Testimonial Collector is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep.

Does Prd V10 Testimonial Collector access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prd V10 Testimonial Collector safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prd V10 Testimonial Collector use?

Prd V10 Testimonial Collector is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prd V10 Testimonial Collector use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prd V10 Testimonial Collector?

Skills that share tags, products or a category with Prd V10 Testimonial Collector: CCPM Project Management (automazeio/ccpm, 8.4k stars), Plaid (BuildGreatProducts/plaid, 218 stars), Project Planner (adrianpuiu/claude-skills-marketplace, 100 stars) and Shep Workstreams (shep-ai/shep, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd V10 Testimonial Collector?

mattgierhart (a GitHub user) maintains it in mattgierhart/PRD-driven-context-engineering, which has 180 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on August 31, 2026.

Source: mattgierhart/PRD-driven-context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.