CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trust-badges-generator

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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/components/conversion/trust-badges/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

As a deprecation stub, the body is exemplary: it states where the capability moved, gives a copy-paste install command, tells the agent exactly what to do next, and explicitly disclaims that this entry contains no component rules. Nothing is padded, missing, or ambiguous for its single redirect purpose.

DimensionReasoningScore

Conciseness

The six-line body contains no concept explanations, no padding, and no information Claude already knows — every sentence (moved notice, install command, follow-up instruction, scope disclaimer) earns its place. Matches the 'lean and efficient' anchor exactly.

5 / 5

Actionability

The body provides a fully executable, copy-paste-ready command ('npx skills add kostja94/bricks --skill component-builder') plus a concrete follow-up instruction ('Ask the agent to use component-builder to build a new Trust Signals'), covering the common case completely.

5 / 5

Workflow Clarity

This is a simple single-task skill and its single action — install the successor and use it — is unambiguous, so the simple-skill exception applies. No destructive or batch operations are involved, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no bundle files (none exist in references/, scripts/, or assets/), and is well organized with a clear heading and one clearly-signaled external reference link. Fits the simple-skill guidance for a top score.

5 / 5

Total

20

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is honest and clear about the skill's deprecated, redirect-only nature, with a concrete successor action. Its weaknesses are the complete absence of 'when to use' trigger guidance and the failure to include the 'trust badges' synonym that matches its own skill name, which limits triggerability for users phrasing the request differently.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when asked to build or add Trust Signals / trust badges') so the stub still triggers reliably on relevant requests.

Include the 'trust badges' synonym (matching the skill name trust-badges-generator) alongside 'Trust Signals' so users phrasing the request either way trigger the redirect.

State explicitly what happens on invocation (redirect to component-builder) so the reader knows the stub itself performs no work.

DimensionReasoningScore

Specificity

Names the domain ("Trust Signals construction") and one concrete action ("install and use component-builder") but offers no broader list of capabilities — fitting the 'domain plus 1-2 concrete actions' anchor. It is not a 2 because the redirect instruction is more concrete than generic domain naming, and not a 4 because only a single action is stated.

3 / 5

Completeness

It clearly answers 'what' ("Deprecated compatibility entry for Trust Signals construction... now maintained in Bricks") but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3. Not a 2 because the 'what' is explicit and unambiguous; not a 4 because the 'when' is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

Relevant keywords like "Trust Signals", "Bricks", and "component-builder" are present, but the description omits the natural synonym "trust badges" even though the skill is named trust-badges-generator, missing common variations a user would say. Not a 4 because that synonym gap means keyword coverage is incomplete rather than just missing 'a few' terms.

3 / 5

Distinctiveness Conflict Risk

The niche ("Trust Signals construction") is specific and the deprecated status plus explicit successor pointer make accidental triggering unlikely, fitting 'mostly distinct; minor overlap risk with closely related skills'. Not a 5 because the badges/signals naming mismatch leaves some residual confusion with sibling component skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

kostja94/marketing-skills

Path

skills/components/conversion/trust-badges/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.