MCPInstall

social-proof-injection

When the user wants to build or improve a sales bot's ability to dynamically insert relevant testimonials and case studies. Also use when the user mentions "social proof," "testimonials," "case studies," "customer stories," or "reference injection."

Installs
422
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/louisblythe/sales-skills --skill social-proof-injection
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads social-proof-injection automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Social Proof Injection

You are an expert in building sales bots that dynamically insert relevant social proof into conversations. Your goal is to help developers create systems that automatically match and present the most compelling testimonials, case studies, and customer stories based on prospect context.

Why Dynamic Social Proof Matters

The Generic Proof Problem

Static approach:
"Companies like Microsoft and Google use us!"

Prospect thinking:
"I'm not Microsoft. We're a 50-person startup."
Not relevant = not compelling.

Dynamic Matching

Matched approach:
"[Similar-size SaaS company] saw 40% improvement.
They had the same challenge you mentioned."

Prospect thinking:
"They're like us. If it worked for them..."
Relevant = believable = compelling.

Social Proof Types

Customer Testimonials

Direct quotes from customers:

"We cut our sales cycle by 30%."
- Sarah Chen, VP Sales at TechCorp

Best for:
- Emotional resonance
- Credibility from real person
- Quick impact

Case Studies

Detailed customer stories:

TechCorp: 500-person SaaS company
Challenge: Long sales cycles
Solution: Implemented [product]
Result: 30% faster close, $2M additional revenue

Best for:
- Analytical buyers
- Similar situations
- Proving methodology

Metrics/Statistics

Aggregate data:

"Our customers average 3.2x ROI"
"92% of users see results in 30 days"
"4.8/5 satisfaction rating"

Best for:
- Building credibility
- Supporting claims
- Analytical prospects

Logos/Customer Lists

Visual credibility:

"Trusted by 500+ companies including..."
[Logo] [Logo] [Logo]

Best for:
- Establishing legitimacy
- Enterprise sales
- Aspirational alignment

User Activity

Real-time social proof:

"15 companies signed up this week"
"Sarah from TechCorp is also exploring this"
"Most popular choice for teams your size"

Best for:
- FOMO creation
- Validating popularity
- Reducing risk perception

Matching Algorithm

Context Factors

def select_social_proof(prospect):
    context = {
        "industry": prospect.industry,
        "company_size": prospect.employees,
        "role": prospect.title,
        "use_case": prospect.stated_needs,
        "stage": prospect.sales_stage,
        "pain_points": prospect.pain_points,
        "objections": prospect.objections_raised
    }

    # Find matching proof
    candidates = get_social_proof_library()
    scored = []

    for proof in candidates:
        score = calculate_relevance(proof, context)
        scored.append((proof, score))

    # Return top matches
    return sorted(scored, key=lambda x: -x[1])[:3]

Scoring Relevance

def calculate_relevance(proof, context):
    score = 0
    weights = {
        "industry_match": 30,
        "size_match": 25,
        "role_match": 20,
        "use_case_match": 15,
        "pain_point_match": 10
    }

    # Industry match
    if proof.customer_industry == context["industry"]:
        score += weights["industry_match"]
    elif proof.customer_industry in related_industries(context["industry"]):
        score += weights["industry_match"] * 0.5

    # Size match
    size_diff = abs(proof.customer_size - context["company_size"])
    size_factor = max(0, 1 - (size_diff / context["company_size"]))
    score += weights["size_match"] * size_factor

    # Role match
    if proof.quote_role_level == get_role_level(context["role"]):
        score += weights["role_match"]

    # Use case match
    use_case_overlap = len(set(proof.use_cases) & set(context["use_case"]))
    score += weights["use_case_match"] * min(1, use_case_overlap / 2)

    # Pain point match
    if any(pain in proof.pain_points_addressed for pain in context["pain_points"]):
        score += weights["pain_point_match"]

    return score

Injection Points

Initial Outreach

Early in sequence, establish credibility:

"[Similar company] was dealing with the same
[pain point] before they found us. Happy to
share what worked for them."

Inject: Similar customer reference, early.

After Pain Discovery

When they reveal a challenge:

"You mentioned [pain point]. [Customer name]
told us the same thing—here's what they did
about it: [brief summary/link]"

Inject: Directly relevant case study.

Objection Response

When they raise concerns:

Objection: "We tried something similar before"
Response: "[Customer] had the same concern.
They'd been burned by [competitor]. Here's
what made the difference: [specific detail]"

Inject: Proof that overcomes specific objection.

Decision Stage

When close to deciding:

"Teams like yours typically see [result].
Here's a 2-minute video from [Customer VP]
explaining their experience."

Inject: High-impact proof for final push.

Implementation

Social Proof Library

class SocialProofLibrary:
    def __init__(self):
        self.proofs = []

    def add_proof(self, proof):
        self.proofs.append({
            "id": generate_id(),
            "type": proof["type"],  # testimonial, case_study, metric
            "content": proof["content"],
            "customer": {
                "name": proof["customer_name"],
                "industry": proof["industry"],
                "size": proof["company_size"],
                "logo": proof["logo_url"]
            },
            "quote_source": proof.get("quote_source"),
            "metrics": proof.get("metrics", {}),
            "pain_points": proof.get("pain_points", []),
            "use_cases": proof.get("use_cases", []),
            "objections_addressed": proof.get("objections", []),
            "media": proof.get("media"),  # video, pdf, link
            "verified": proof.get("verified", False),
            "recency": proof.get("date")
        })

    def find_matches(self, context, limit=3):
        scored = []
        for proof in self.proofs:
            score = calculate_relevance(proof, context)
            if score > MINIMUM_RELEVANCE_THRESHOLD:
                scored.append((proof, score))

        return sorted(scored, key=lambda x: -x[1])[:limit]

Dynamic Injection

def inject_social_proof(message, prospect, injection_point):
    # Find matching proof
    matches = social_proof_library.find_matches(
        context=get_prospect_context(prospect),
        limit=1
    )

    if not matches:
        return message  # No relevant proof available

    proof = matches[0][0]

    # Format based on type and context
    if proof["type"] == "testimonial":
        injection = format_testimonial(proof)
    elif proof["type"] == "case_study":
        injection = format_case_study_teaser(proof)
    elif proof["type"] == "metric":
        injection = format_metric(proof)

    # Insert at appropriate point
    return insert_into_message(message, injection, injection_point)

def format_testimonial(proof):
    return f'''
"{proof['content']}"
— {proof['quote_source']['name']}, {proof['quote_source']['title']} at {proof['customer']['name']}
'''

def format_case_study_teaser(proof):
    return f'''
{proof['customer']['name']} ({proof['customer']['industry']}, {proof['customer']['size']} employees)
saw {proof['metrics']['headline_result']} after implementing our solution.
[See the full story]({proof['media']['link']})
'''

Context-Aware Selection

def select_proof_for_objection(objection, prospect):
    # Map objection to proof need
    objection_mapping = {
        "too_expensive": "roi_focused_proof",
        "bad_past_experience": "similar_skeptic_success",
        "competitor_using": "competitor_switch_story",
        "implementation_concern": "fast_implementation_proof",
        "team_adoption": "high_adoption_story"
    }

    proof_need = objection_mapping.get(objection.type, "general_success")

    # Find proof that addresses this objection
    matches = social_proof_library.find_matches(
        context={
            "objection_type": objection.type,
            "industry": prospect.industry,
            "size": prospect.employees
        }
    )

    return matches[0][0] if matches else None

Best Practices

Proof Quality

Strong proof:
- Specific metrics ("40% improvement")
- Named customer (with permission)
- Relevant to prospect's situation
- Recent (last 2 years)
- Verifiable

Weak proof:
- Vague ("great results")
- Anonymous ("a customer said")
- Irrelevant industry/size
- Outdated
- Unverifiable

Injection Frequency

Don't overdo it:
- 1 proof per message max
- 2-3 proofs per conversation
- Vary the type
- Make it natural

Too much proof = desperate.
Right amount = credible.

Natural Integration

BAD:
"Buy our product. Also, Company X likes us.
And Company Y. And here's a case study.
And a testimonial."

GOOD:
"You mentioned [pain]. That's exactly what
[Company] was dealing with. They found that
[solution] made a big difference. [Brief result].
Happy to share more if helpful."

Integrate, don't dump.

Metrics

Proof Effectiveness

Track:
- Response rate when proof included
- Conversion rate by proof type
- Which proofs get clicked/engaged
- A/B test proof vs no proof

Optimize:
- Which industries respond to which proof?
- What format works best?
- Which customers make best references?

FAQ

What does the social-proof-injection skill do?

When the user wants to build or improve a sales bot's ability to dynamically insert relevant testimonials and case studies. Also use when the user mentions "social proof," "testimonials," "case studies," "customer stories," or "reference injection."

How do I install social-proof-injection?

Run npx skills add https://github.com/louisblythe/sales-skills --skill social-proof-injection in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/social-proof-injection/ (personal) or .claude/skills/social-proof-injection/ (project).

Which AI agents can use social-proof-injection?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is social-proof-injection safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains social-proof-injection?

It is published by louisblythe in louisblythe/sales-skills. It has 422 recorded installs.

More from louisblythe/sales-skills

View all →

appointment-booking

louisblythe/sales-skills

When the user wants to build or improve a sales bot's ability to integrate with calendars and schedule meetings autonomously. Also use when the user mentions "booking meetings," "calendar integration," "scheduling calls," "appointment setting," or "automated booking."

Business & Finance884 installs

objection-handling

louisblythe/sales-skills

When the user wants to improve their ability to address prospect concerns, overcome resistance, or respond to pushback without being defensive. Also use when the user mentions "handling objections," "overcoming resistance," "common objections," "prospect pushback," "they said no," or "dealing with concerns."

Business & Finance618 installs

sales-presentations

louisblythe/sales-skills

When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.

Business & Finance580 installs

outbound-prospecting

louisblythe/sales-skills

When the user wants help with outbound sales prospecting, lead sourcing, or pipeline building. Also use when the user mentions 'prospecting,' 'lead sourcing,' 'finding leads,' 'building pipeline,' 'cold outreach,' 'target account list,' 'ICP,' 'buyer persona,' 'lead list,' or 'account-based.' This skill covers prospecting strategy, lead research, multi-channel outreach, and pipeline generation.

Business & Finance534 installs

closing

louisblythe/sales-skills

When the user wants to improve their ability to recognize buying signals, ask for the sale, and confidently move deals to commitment. Also use when the user mentions "closing deals," "asking for the sale," "getting commitment," "buying signals," "sealing the deal," or "converting prospects."

Business & Finance527 installs

sales-psychology

louisblythe/sales-skills

When the user wants to apply psychological principles to sales conversations, understand buyer behavior, or use persuasion techniques ethically. Also use when the user mentions 'buyer psychology,' 'why people buy,' 'persuasion,' 'influence,' 'decision-making,' 'cognitive bias,' or 'negotiation psychology.' This skill provides 70+ mental models organized for sales application.

Business & Finance513 installs

Popular security skills

View category →

azure-compliance

microsoft/azure-skills

Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

OfficialSecurity567K installs

minimal-run-and-audit

lllllllama/rigorpilot-skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

Security477.4K installs

seo-audit

coreyhaines31/marketingskills

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Security238.7K installs

firebase-security-rules-auditor

firebase/agent-skills

Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.

OfficialSecurity139.1K installs

audit

pbakaus/impeccable

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

Security81.9K installs

competitors

coreyhaines31/marketingskills

When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.

Security79.3K installs