mcpbeat

Trust Badges Generator

kostja94/trust-badges-generator

When the user wants to add or optimize trust badges, "Trusted by" logos, security seals, or social proof elements. Also use when the user mentions "trust badges," "trusted by," "security badges," "payment logos," "social proof," "trust seals," "SSL badge," "customer logos," "as seen in," or "trust signals." For press logos, use press-coverage-page-generator.

938 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kostja94/marketing-skills --skill trust-badges-generator

The instruction itself

11 sections, as written by the author

Components: Trust Badges

Guides trust badge design and placement for conversion. Trust badges borrow authority from third-party organizations to signal legitimacy and reduce purchase anxiety.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for key partners and certifications.

Identify:

  • Site type: E-commerce, SaaS, lead gen
  • Available badges: Security, payment, reviews, guarantees
  • Placement goals: Hero, checkout, product pages

Badge Types & Impact

| Type | Best Placement | Conversion Impact |

|------|----------------|-------------------|

| Security (SSL, Norton, McAfee) | Checkout, payment forms | +15–10% for unfamiliar brands |

| Payment logos (Visa, PayPal, Stripe) | Checkout, cart | +8→2% trust |

| Money-back guarantee | Product, checkout | +6–10% |

| Reviews/ratings (Trustpilot, BBB) | Product, hero | +12→8% |

| Privacy/compliance (GDPR, CCPA) | Forms, checkout | Data-sensitive transactions |

"Trusted by" logos: Client/customer logos in hero or footer; social proof for B2B. "As Seen In" (press coverage): Publication logos; see press-coverage-page-generator for media mentions aggregation.

Best Practices

Quantity

  • 3→ badge types max; more can cause "badge bloat" and reduce conversions by 5→%
  • Quality over quantity; use only legitimate, verifiable badges

Placement

  • Highest leverage: Cart and checkout (near payment fields)
  • Product pages: Near add-to-cart button
  • Hero: "Trusted by" logos for brand credibility
  • Footer: Secondary trust signals

Authenticity

  • Use only real, verifiable badges
  • Fake or irrelevant badges create skepticism
  • Link to verification where appropriate

Design Guidelines

  • Consistent size and style; don't mix clashing visuals
  • Image optimization: Alt text, format—see image-optimization
  • Adequate spacing; avoid clutter
  • Grayscale or muted for "Trusted by" logos (don't compete with primary content)
  • Ensure badges are recognizable at display size

Accessibility

  • Provide alt text for badge images (e.g., "Norton Secured")
  • Don't rely on badges alone for critical information

Output Format

  • Badge recommendations by type and placement
  • Placement map (hero, product, checkout)
  • Quantity guidance (avoid bloat)
  • landing-page-generator: Trust signals as step 2 (earn trust) in landing page flow
  • hero-generator: "Trusted by" often in hero
  • testimonials-generator: Complementary social proof
  • cta-generator: Badges near CTAs increase conversion
  • pricing-page-generator: Trust badges on pricing pages
  • image-optimization: Badge image optimization (alt, format)
  • press-coverage-page-generator: "As Seen In" publication logos; similar visual treatment; distinct (press = media coverage; trust-badges = security, payment, reviews)
  • brand-protection: "Official website" badges to distinguish from impersonation sites

How to use it

Copy the folder

Take kostja94/trust-badges-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.