social-proof-architect
One sentence - what this skill does and when to invoke it
What this skill does
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 in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.