Skip to main content
skill CX Codex

trust-badges-generator — Claude Code skill: moved to Bricks

A stub skill: Trust Signals construction now lives in Bricks, and this entry only records the move. Worth installing if an old config still points at it.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add kostja94/marketing-skills --skill trust-badges-generator -a claude-code
npx skills add kostja94/marketing-skills --skill trust-badges -a claude-code
Open on GitHub

What trust-badges-generator does

This skill no longer builds Trust Signals. It carries no component rules and is not maintained: the metadata marks it as moved, with kostja94/bricks/component-builder named as the successor. All the file does is tell the agent where construction went.

Trust Signals construction is now kept in Bricks, the component layer for AI agents, in the Trust Signals reference inside the component-builder skill. For a working version, install that one: npx skills add kostja94/bricks --skill component-builder. Then ask the agent to build new Trust Signals with component-builder.

If trust-badges-generator already sits in your config, nothing breaks — the entry just stops affecting generation. Don't expect new rules from it, because there are none here.

What it helps with

  • Find where Trust Signals construction moved
  • Replace a deprecated skill with the current one
  • Install component-builder from Bricks
  • Keep an old config with trust-badges-generator from breaking

Example prompts for the agent

  • Show me where Trust Signals construction moved
  • Install the component-builder skill from Bricks and build new Trust Signals
  • Check that my config only has the trust-badges-generator stub entry left

How to install trust-badges-generator

1Skills CLI (Vercel)

npx skills add kostja94/marketing-skills --skill trust-badges-generator -a claude-code
npx skills add kostja94/marketing-skills --skill trust-badges -a claude-code

2Manually: put the files in place

~/.claude/skills/trust-badges/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/trust-badges/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about trust-badges-generator

How do I install trust-badges-generator in Claude?

npx skills add kostja94/marketing-skills --skill trust-badges-generator -a claude-code. That only gives you the move notice: for working construction, run npx skills add kostja94/bricks --skill component-builder.

What does trust-badges-generator do?

It builds nothing. It is a compatibility entry that tells the agent Trust Signals construction now lives in Bricks.

What should I use instead of trust-badges-generator?

The component-builder skill from the kostja94/bricks repository, which holds the Trust Signals reference.

Source text

SKILL.md · MIT
---
name: trust-badges-generator
description: Deprecated compatibility entry for Trust Signals construction. This component is now maintained in Bricks; install and use component-builder to build a new Trust Signals.
metadata:
  status: moved
  successor: kostja94/bricks/component-builder
---

# Trust Signals construction has moved

Trust Signals construction is now maintained in the [Trust Signals reference](https://github.com/kostja94/bricks/blob/main/skills/component-builder/references/components/trust-signals.md) in [Bricks](https://github.com/kostja94/bricks), the component layer for AI agents.

```bash
npx skills add kostja94/bricks --skill component-builder
```

Ask the agent to use component-builder to build a new Trust Signals. This compatibility entry contains no component rules and is no longer maintained.

© kostja94 · MIT · kostja94/marketing-skills

Similar skills

Everything for Marketing and content →

From the same set125

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor