Token导航 LogoToken导航

Agent Skill · 效率

brw-testimonial-collector(BRW 推荐收藏家)

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

brw-testimonial-collector 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 3,055。

总安装 19,872周安装 828GitHub Stars 公开资料未说明下载 6,624核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:brw-testimonial-collector(BRW 推荐收藏家)
来源仓库:https://github.com/brianrwagner/brw-testimonial-collector
安装命令:
openclaw skills install brw-testimonial-collector
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install brw-testimonial-collector

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

系统化收集并格式化客户评价,用于社会证明建设。适合需要收集反馈或转化满意客户为推荐资源时调用。通过 clawhub 安装,需确认权限范围和维护状态。涉及客户数据时应脱敏并遵守隐私规范。brw-testimonial-collector 属于效率类 Skill,可作为该场景下的辅助能力补充。

建议结合原始 README 核验整理渠道与合规边界。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install brw-testimonial-collector;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

brw-testimonial-collector 怎么安装?

在终端执行 openclaw skills install brw-testimonial-collector。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

brw-testimonial-collector 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

brw-testimonial-collector 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

brw-testimonial-collector 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

brw-testimonial-collector 用的人多吗?

公开数据是累计安装 19,872 次,近一周安装 828 次,下载 6,624 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

brw-testimonial-collector 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
brw-testimonial-collector

BRW 推荐收藏家 · 本页

19,872—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
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 public advocates.

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

LocationFormatPurpose
HomepageShortTrust at first glance
Sales pagesMediumOvercome objections
ProposalsMediumRelevant proof
LinkedInShortCredibility
Case studiesLongDeep 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:

ClientDateQuoteFormatPermissionUsed 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*

平台分布

OpenClaw

78.22%
按下载量换算5,181

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills