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.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for key partners and certifications.
Identify:
| 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.
alt text for badge images (e.g., "Norton Secured")Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/trust-badges · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/trust-badges"
cp -r "skills/components/conversion/trust-badges" ".claude/skills/trust-badges"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.