Customer Evidence Collector

Social proof mining

by Ootto-AI · MIT license · ★ 139 on GitHub

Social proof mining cover

Use when you need to locate and prepare already-approved customer evidence for a social campaign, profile, post, or sales-adjacent explanation. Trigger phrases include "find proof we can use", "what customer evidence supports this?",…

---
name: social-proof-mining
description: Use when you need to locate and prepare already-approved customer evidence for a social campaign, profile, post, or sales-adjacent explanation. Trigger phrases include "find proof we can use", "what customer evidence supports this?", "mine testimonials", "turn these outcomes into social proof", and "which quote backs this claim?". Do not use this to fabricate testimonials, imply endorsement, expose private customer information, or turn a single anecdote into a performance promise; use social-listening for broad feedback patterns and positioning-audit for the message itself.
---

# Social Proof Mining

Build an approval-safe proof library that links every useful claim to a real source, permission status, and context.

## 1. Gather only traceable evidence

Ask for approved testimonials, case studies, reviews, customer messages, performance data, or public posts along with their source, date, owner, and permission status. Keep evidence that is merely interesting separate from evidence cleared for marketing use.

## 2. Match proof to a narrow claim

For each item, identify exactly what it supports: a workflow, a customer situation, a qualitative benefit, or a measured outcome. Preserve the conditions around it. If a quote says a customer saved time in one context, do not rewrite it as a universal productivity claim.

## 3. Create usable proof units

Overview

Build an approval-safe proof library that links every useful claim to a real source, permission status, and context.

Manual install (npx, ZIP)
Claude Codenpx skills add Ootto-AI/claude-content-skills --skill social-proof-mining -g -a claude-code
Claude Code (degit)npx degit Ootto-AI/claude-content-skills/skills/social-proof-mining#main ~/.claude/skills/social-proof-mining
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.2 KB
Read SKILL.md here
Ootto-AI/main1 file shown
SKILL.md
Show the full text46 lines

Social Proof Mining

Build an approval-safe proof library that links every useful claim to a real source, permission status, and context.

1. Gather only traceable evidence

Ask for approved testimonials, case studies, reviews, customer messages, performance data, or public posts along with their source, date, owner, and permission status. Keep evidence that is merely interesting separate from evidence cleared for marketing use.

2. Match proof to a narrow claim

For each item, identify exactly what it supports: a workflow, a customer situation, a qualitative benefit, or a measured outcome. Preserve the conditions around it. If a quote says a customer saved time in one context, do not rewrite it as a universal productivity claim.

3. Create usable proof units

Return a proof card with the exact source wording, approved short form, claim it supports, required attribution or disclosure, usage limits, and a note on context. Flag anything that needs customer, legal, or product approval before it can be published.

4. Choose the smallest truthful placement

Recommend where each proof unit helps: a post, profile, campaign brief, creator brief, or comparison explanation. Pair proof with the claim it verifies. If proof is weak or stale, say so and route to a request for better evidence instead of polishing it into certainty.

Hard rules

  • Never invent, composite, or substantially rewrite a customer quote.
  • Do not use names, handles, logos, screenshots, DMs, or identifiable outcomes without appropriate permission.
  • Preserve scope, timeframe, and conditions for any numeric result.
  • Do not imply that one customer represents all customers or guaranteed results.
  • Separate public evidence from private feedback and respect every usage restriction.

Failure modes

Failure Do this instead
A compelling quote has no permission record Mark it unavailable until the owner confirms usage rights.
Proof is detached from its conditions Keep the original context beside the approved claim.
Testimonials become generic praise Match each item to a specific audience concern or claim.
A campaign needs proof that does not exist Narrow the promise or create a demonstration, not a false testimonial.

Where it sits

Use social-listening to identify recurring customer language; use this skill to isolate approved evidence. Feed the output into positioning-audit, campaign-brief, linkedin-thought-leadership, and influencer-partnerships. Use audience-personas only for grouped patterns, never to disclose individual customer data.

1---
2name: social-proof-mining
3description: Use when you need to locate and prepare already-approved customer evidence for a social campaign, profile, post, or sales-adjacent explanation. Trigger phrases include "find proof we can use", "what customer evidence supports this?", "mine testimonials", "turn these outcomes into social proof", and "which quote backs this claim?". Do not use this to fabricate testimonials, imply endorsement, expose private customer information, or turn a single anecdote into a performance promise; use social-listening for broad feedback patterns and positioning-audit for the message itself.
4---
5 
6# Social Proof Mining
7 
8Build an approval-safe proof library that links every useful claim to a real source, permission status, and context.
9 
10## 1. Gather only traceable evidence
11 
12Ask for approved testimonials, case studies, reviews, customer messages, performance data, or public posts along with their source, date, owner, and permission status. Keep evidence that is merely interesting separate from evidence cleared for marketing use.
13 
14## 2. Match proof to a narrow claim
15 
16For each item, identify exactly what it supports: a workflow, a customer situation, a qualitative benefit, or a measured outcome. Preserve the conditions around it. If a quote says a customer saved time in one context, do not rewrite it as a universal productivity claim.
17 
18## 3. Create usable proof units
19 
20Return a proof card with the exact source wording, approved short form, claim it supports, required attribution or disclosure, usage limits, and a note on context. Flag anything that needs customer, legal, or product approval before it can be published.
21 
22## 4. Choose the smallest truthful placement
23 
24Recommend where each proof unit helps: a post, profile, campaign brief, creator brief, or comparison explanation. Pair proof with the claim it verifies. If proof is weak or stale, say so and route to a request for better evidence instead of polishing it into certainty.
25 
26## Hard rules
27 
28- Never invent, composite, or substantially rewrite a customer quote.
29- Do not use names, handles, logos, screenshots, DMs, or identifiable outcomes without appropriate permission.
30- Preserve scope, timeframe, and conditions for any numeric result.
31- Do not imply that one customer represents all customers or guaranteed results.
32- Separate public evidence from private feedback and respect every usage restriction.
33 
34## Failure modes
35 
36| Failure | Do this instead |
37| --- | --- |
38| A compelling quote has no permission record | Mark it unavailable until the owner confirms usage rights. |
39| Proof is detached from its conditions | Keep the original context beside the approved claim. |
40| Testimonials become generic praise | Match each item to a specific audience concern or claim. |
41| A campaign needs proof that does not exist | Narrow the promise or create a demonstration, not a false testimonial. |
42 
43## Where it sits
44 
45Use social-listening to identify recurring customer language; use this skill to isolate approved evidence. Feed the output into positioning-audit, campaign-brief, linkedin-thought-leadership, and influencer-partnerships. Use audience-personas only for grouped patterns, never to disclose individual customer data.
46 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 139
Checked
Source
Ootto-AI/claude-content-skills ↗
Creator
Ootto-AI · 36 listings
View creator

Similar skills

See all →

More from Ootto-AI

SkillHook Variant A/B GeneratorOotto-AI/claude-content-skills · by Ootto-AIGenerates two genuinely distinct hook variants for the same reel so you can post-test which opening actually wins. Use when the user says "give me two hooks to test", "A/B this hook", "which opening should I use", "hook variants".★ 139 GitHub starsSkillInternet Research RouterOotto-AI/claude-content-skills · by Ootto-AIMUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, V2EX, LinkedIn/领英/招聘/求职/jobs, YouTube, GitHub code search, 小宇宙播客, 雪球/股票行情, RSS feeds, or any web URL. 13 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: 写报告/数据分析/翻译等内容加工(本 skill 只负责从互联网获取内容); 发帖/评论/点赞等写操作;已有专门 skill 的平台(先用专门 skill)。 【路由方式】SKILL.md 包含路由表和常用命令,复杂场景需按需阅读对应分类的 references/*.md。 分类:search / social (小红书/推特/B站/V2EX/Reddit) / career(LinkedIn) / dev(github) / web(网页/文章/RSS) / video(YouTube/B站/播客)。★ 139 GitHub starsSkillObsidian Long-Term MemoryOotto-AI/claude-content-skills · by Ootto-AIGive Claude a permanent, searchable long-term memory using an Obsidian vault as the store. At the end of a session, summarize what mattered and save it as a Markdown note in your "AI Brain" vault; at the start of a session (or on demand), read back only the relevant past notes. Local markdown you own — connected via the Filesystem MCP. Trigger with "wrap up", "save this session", or "remember this".★ 139 GitHub starsSkillAnalytics Readout TranslatorOotto-AI/claude-content-skills · by Ootto-AIReads your reel insights and explains in plain English what to make more of and what to stop — no jargon. Use when the user says "explain my analytics", "what do my numbers mean", "read my insights", "how did this reel do".★ 139 GitHub starsSkillSocial Audience PersonasOotto-AI/claude-content-skills · by Ootto-AIBuild evidence-led social audience personas from customer interviews, comments, reviews, or CRM notes.★ 139 GitHub starsSkillSocial Profile ConverterOotto-AI/claude-content-skills · by Ootto-AIRewrites your bio, name field and pinned-reel order to convert profile visits into follows and clicks. Use when the user says "rewrite my bio", "optimize my profile", "what should my bio say", "which reels should I pin".★ 139 GitHub stars