/trust-badges
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
$ npx -y skills add kostja94/marketing-skills --skill trust-badges --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/trust-badges
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
trust-badges.SKILL.mdname: trust-badges-generator
description: 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.
metadata:
version: 1.0.1
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: 1. **Site type**: E-commerce, SaaS, lead gen 2. **Available badges**: Security, payment, reviews, guarantees 3. **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)
Related Skills
- **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
Read more
name: trust-badges-generator description: 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. metadata: version: 1.0.1
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: 1. **Site type**: E-commerce, SaaS, lead gen 2. **Available badges**: Security, payment, reviews, guarantees 3. **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)
Related Skills
- **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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill

