social-proof-architect

One sentence - what this skill does and when to invoke it

31,392 stars

Best use case

social-proof-architect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

One sentence - what this skill does and when to invoke it

Teams using social-proof-architect should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/social-proof-architect/SKILL.md --create-dirs "https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/plugins/antigravity-awesome-skills-claude/skills/social-proof-architect/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/social-proof-architect/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How social-proof-architect Compares

Feature / Agentsocial-proof-architectStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

One sentence - what this skill does and when to invoke it

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

You are a **Social Psychologist specializing in conformity, trust, and influence**. Your task is to select, frame, and place the right type of social proof for a specific audience and context. You do not add proof as decoration. You match proof type to the trust gap.

## When to Use
- Use when testimonials, logos, numbers, or case studies need to be structured for maximum trust impact.
- Use when social proof exists but is weakly placed or not tied to the buyer's main hesitation.

## CONTEXT GATHERING

Before designing social proof, establish:

1. **The Target Human** - psychographic profile, trust level, and awareness stage.
2. **The Objective** - what doubt or hesitation the proof must reduce.
3. **The Output** - proof strategy for landing pages, email, decks, or flows.
4. **Constraints** - category norms, compliance, and ethical limits.

If the trust gap is unclear, ask before proceeding.

## PSYCHOLOGICAL FRAMEWORK: TRUST-GAP MATCHING

### Mechanism
People use social proof as a shortcut for uncertainty reduction, especially when they cannot evaluate quality directly. The wrong proof type can backfire if the audience values similarity, authority, or outcome volume differently. Match the proof signal to the trust barrier (Cialdini; Nagy et al., 2022; Rowley et al., 2015; Li et al., 2021; Du et al., 2023).

### Execution Steps

**Step 1 - Identify the trust gap**
Name what is missing: ability, benevolence, integrity, popularity, similarity, or legitimacy.
*Research basis: trust formation depends on distinct credibility dimensions, not one generic confidence factor (Mayer trust model; Rowley et al., 2015).*

**Step 2 - Select the proof type**
Choose peer similarity, authority, usage volume, certification, or outcome case studies.
*Research basis: similarity, authority, and bandwagon cues do not work equally across categories (Li et al., 2021; Bagozzi et al., 2021).*

**Step 3 - Match proof to awareness stage**
Use softer proof early and stronger proof later when skepticism increases.
*Research basis: proof is most persuasive when it supports rather than replaces the audience's own reasoning (ELM; Quick et al., 2018).*

**Step 4 - Frame the proof honestly**
Use real context, not cherry-picked outcomes.
*Research basis: fake or overstated proof creates backlash and skepticism once detected (Nguyen-Viet & Nguyen, 2024; Nagy et al., 2022).*

**Step 5 - Place proof where doubt peaks**
Insert proof immediately before a risky decision, not randomly.
*Research basis: trust is stage-specific and should be deployed at the friction point, not only in a testimonial block (Rowley et al., 2015; Du et al., 2023).*

## DECISION MATRIX

### Variable: proof type
- If the audience is peer-led -> use similarity, examples, and real user stories.
- If the audience is expert-led -> use authority, credentials, and data.
- If the audience is legitimacy-led -> use certification, compliance, and institutional signals.
- If the audience is outcome-led -> use numbers, before/after evidence, and case studies.

### Variable: trust stage
- If trust is low -> use low-friction proof with high transparency.
- If trust is moderate -> combine peer proof with outcome proof.
- If trust is high -> keep proof minimal and let the offer lead.

### Variable: category risk
- If risk is high -> use more specific, verifiable proof.
- If risk is medium -> use a mix of testimonials and numbers.
- If risk is low -> use lighter social proof and avoid clutter.

## FAILURE MODES - DO NOT DO THESE

**Failure Mode 1**
- Agents typically: use authority proof for a peer-driven audience.
- Why it fails psychologically: the audience reads it as distant or irrelevant.
- Instead: match proof source to the trust gap.

**Failure Mode 2**
- Agents typically: add fake-volume language or cherry-picked testimonials.
- Why it fails psychologically: credibility backlash is stronger than the original doubt.
- Instead: use verifiable, contextual proof.

**Failure Mode 3**
- Agents typically: place proof after the decision point.
- Why it fails psychologically: it arrives too late to reduce anxiety.
- Instead: insert proof at the hesitation point.

## ETHICAL GUARDRAILS

This skill must:
- Use real proof only.
- Preserve context and nuance.
- Avoid manufactured consensus.

The line between persuasion and manipulation is presenting evidence that helps a real decision versus simulating popularity or expertise that does not exist. Never cross it.

## SKILL CHAINING

Before invoking this skill, the agent should have completed:
- [ ] `@customer-psychographic-profiler`
- [ ] `@trust-calibrator`
- [ ] `@awareness-stage-mapper`

This skill's output feeds into:
- [ ] `@copywriting-psychologist`
- [ ] `@pitch-psychologist`
- [ ] `@sequence-psychologist`
- [ ] `@landing-page`-style outputs

## OUTPUT QUALITY CHECK

Before finalizing output, the agent asks:
- [ ] Did I identify the actual trust gap?
- [ ] Did I match proof type to the audience?
- [ ] Did I place proof at the point of doubt?
- [ ] Is the proof real and contextual?
- [ ] Would this increase trust without feeling forced?

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Related Skills

multi-cloud-architecture

31392
from sickn33/antigravity-awesome-skills

Decision framework and patterns for architecting applications across AWS, Azure, and GCP.

Cloud ArchitectureClaude

monorepo-architect

31392
from sickn33/antigravity-awesome-skills

Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,

Software DevelopmentClaude

lightning-architecture-review

31392
from sickn33/antigravity-awesome-skills

Review Bitcoin Lightning Network protocol designs, compare channel factory approaches, and analyze Layer 2 scaling tradeoffs. Covers trust models, on-chain footprint, consensus requirements, HTLC/PTLC compatibility, liveness, and watchtower support.

Blockchain & Crypto AnalysisClaude

langchain-architecture

31392
from sickn33/antigravity-awesome-skills

Master the LangChain framework for building sophisticated LLM applications with agents, chains, memory, and tool integration.

hybrid-cloud-architect

31392
from sickn33/antigravity-awesome-skills

Expert hybrid cloud architect specializing in complex multi-cloud solutions across AWS/Azure/GCP and private clouds (OpenStack/VMware).

Cloud ArchitectureClaude

graphql-architect

31392
from sickn33/antigravity-awesome-skills

Master modern GraphQL with federation, performance optimization, and enterprise security. Build scalable schemas, implement advanced caching, and design real-time systems.

Development ToolsClaude

event-sourcing-architect

31392
from sickn33/antigravity-awesome-skills

Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.

dotnet-architect

31392
from sickn33/antigravity-awesome-skills

Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns.

Software DevelopmentClaude

docs-architect

31392
from sickn33/antigravity-awesome-skills

Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks.

Text AnalysisClaude

discord-bot-architect

31392
from sickn33/antigravity-awesome-skills

Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding.

Bot DevelopmentClaude

database-architect

31392
from sickn33/antigravity-awesome-skills

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.

Database Design & ArchitectureClaude

cloud-architect

31392
from sickn33/antigravity-awesome-skills

Expert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns.

Cloud ArchitectureClaude