agentleFS
fjilvvifjilvvi/growthlens/skills/social-proof-audit/SKILL.md

social-proof-audit

Skill2 starsChanged 5 months agoMITView on GitHub

Audit the social proof and trust signals on a site — testimonials, case studies, reviews, logos, ratings, guarantees, authority and security badges — for credibility, placement, and specificity, and flag manipulative or fake trust tactics. Use when the user asks to "audit social proof", "review the testimonials / trust signals", "is this credible", "why don't visitors trust this page", or studies how a competitor builds trust and urgency.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    If reviewing your own page, ask what objection most often stops buyers.

    line 42
  2. Distinctive:

    Call out fake/manipulative trust tactics plainly.

    line 102
  3. Distinctive:

    Don't assume a claim is true or false you can't verify — mark it "unverifiable".

    line 103

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social Proof & Trust Audit

Judge whether a site's proof actually builds trust — and call out the fake or manipulative tactics.

What it does

Inventories every trust and social-proof element on a site, evaluates each for credibility, specificity, and placement relative to the decision point, and flags manipulative patterns (fake scarcity, unverifiable claims, dark patterns). Returns a trust scorecard and prioritized fixes — or, for a competitor, a read on how they manufacture trust.

When to use this skill

  • "Audit the social proof / trust signals on this page."
  • "Are these testimonials credible? Why won't people trust this?"
  • "Review the trust and urgency tactics on <competitor>."
  • Pre-launch credibility check on a sales or landing page.

Inputs needed

  • Required: the page or site URL (or screenshots).
  • Helpful: the conversion goal and the audience's main fears/objections — proof is only effective when it answers a real anxiety.
  • If reviewing your own page, ask what objection most often stops buyers.

Method

  1. Inventory trust elements:
    • Testimonials (named? photo? role/company? specific result?)
    • Case studies (with real numbers and a clear before/after?)
    • Third-party reviews/ratings (G2, Trustpilot, app store, Google)
    • Customer/partner logos and counts ("10,000+ users")
    • Guarantees / refund terms / risk reversal
    • Authority signals (press, awards, certifications, expert endorsements)
    • Security/compliance badges (SSL, payment, GDPR, SOC2)
    • Urgency/scarcity (timers, limited seats, cart close)
  2. Grade each on credibility & specificity — named + specific + verifiable beats anonymous + vague. Specific numbers and real identities score highest.
  3. Check placement — does proof appear at the decision points (near CTAs, pricing, forms) and match the objection at that moment?
  4. Match proof to objections — list the buyer's likely fears and whether a proof element answers each. Find unaddressed objections.
  5. Flag manipulation — fake/perma countdown timers, "results not typical" income claims, invented review counts, fake activity popups, pressure tactics. Note these honestly; recommend ethical alternatives.
  6. Score & recommend — a trust score plus prioritized fixes (add, strengthen, reposition, or remove).

Output format

# Social Proof & Trust Audit — <page>

## TL;DR
- Trust score __/5. The biggest credibility gap, and any manipulative tactics found.

## Trust inventory
| Element | Present? | Credibility (specific/named/verifiable) | Placement |
|---------|----------|------------------------------------------|-----------|
| Testimonials | | | |
| Case studies | | | |
| Reviews / ratings | | | |
| Logos / counts | | | |
| Guarantee | | | |
| Authority signals | | | |
| Security badges | | | |
| Urgency / scarcity | | | |

## Proof ↔ objection match
| Likely objection | Addressed by | Gap? |
|------------------|--------------|------|

## Manipulative / risky tactics
- (List, with an ethical alternative for each.)

## Prioritized fixes
| # | Fix | Element | Why | Impact | Effort |
|---|-----|---------|-----|--------|--------|

Quality bar

  • Rate proof by specificity and verifiability, not quantity.
  • Call out fake/manipulative trust tactics plainly; never recommend them.
  • Don't assume a claim is true or false you can't verify — mark it "unverifiable".
  • Tie missing proof to the specific objection it would resolve.

Common mistakes to avoid

  • Counting testimonials instead of judging their credibility.
  • Ignoring placement — strong proof in the footer does little at the CTA.
  • Praising urgency tactics that are obviously fake.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.