social-proof-mining
Skill417 starsChanged 3 months agoMITView on GitHub
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.
In this repository54 other files it gives its agents.
- ab-hook-testerSkill
- agent-reachSkill
- ai-brainSkill
- analytics-readoutSkill
- audience-personasSkill
- best-time-schedulerSkill
- bio-profile-optimizerSkill
- b-roll-shot-listSkill
- campaign-briefSkill
- caption-and-hashtagsSkill
- carousel-builderSkill
- collab-outreachSkill
- comment-miningSkill
- comment-responderSkill
- community-engagement-planSkill
- competitor-positioningSkill
- competitor-teardownSkill
- content-auditSkill
- content-calendarSkill
- content-factorySkill
- content-pillar-builderSkill
- content-repurposerSkill
- content-researchSkill
- cover-thumbnail-briefSkill
- creator-outreachSkill
- cross-platform-distributionSkill
- cross-platform-reformatterSkill
- cta-writerSkill
- dm-script-writerSkill
- going-viralSkill
- hashtag-keyword-researchSkill
- hook-miningSkill
- humanizerSkill
- influencer-partnershipsSkill
- launch-retrospectiveSkill
- linkedin-thought-leadershipSkill
- on-screen-text-writerSkill
- paid-social-briefSkill
- positioning-auditSkill
- profile-conversion-auditSkill
- reel-analyzerSkill
- reel-builderSkill
- reel-scripterSkill
- series-plannerSkill
- social-analytics-reportSkill
- social-listeningSkill
- story-sequencerSkill
- trend-spotterSkill
- ugc-creator-briefSkill
- utm-campaign-planSkill
- viral-carouselSkill
- viral-hook-writerSkill
- viralitySkill
- x-thread-strategySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Ask for approved testimonials, case studies, reviews, customer messages, performance data, or public posts along with their source, date, …
- Distinctive: line 28
Never invent, composite, or substantially rewrite a customer quote.
- Distinctive: line 29
Do not use names, handles, logos, screenshots, DMs, or identifiable outcomes without appropriate permission.
- Distinctive: line 31
Do not imply that one customer represents all customers or guaranteed results.
- Distinctive: line 45
Use social-listening to identify recurring customer language.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

