CtrlK
BlogDocsLog inGet started
Tessl Logo

trust-signals

Use when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content. Use when auditing E-E-A-T or conversion optimization.

46

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/trust-signals/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is well-structured, concise, and uses progressive disclosure effectively by deferring detail to a real reference file. Its weaknesses are minor redundancy around E-E-A-T/YMYL and the lack of in-body executable examples or an explicit validate-and-reverify loop.

Suggestions

Consolidate the repeated E-E-A-T / YMYL / Quality Rater Guidelines rationale into a single statement to remove the duplicated bullets and intro sentence.

Add at least one concrete in-body example (e.g., a JSON-LD review snippet or a Trustpilot widget embed) so the Fix guidance is copy-paste ready, not just descriptive.

Add an explicit verification checkpoint after Fix (e.g., re-check that badges link to a live source and structured data validates) to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, but the E-E-A-T / YMYL / Google Quality Rater Guidelines point is restated across the intro, two Quick Reference bullets, and the Explain section, which could be tightened into one statement.

2 / 3

Actionability

Check and Fix name concrete, specific items (Trustpilot/Google review widgets, security badges near forms, verifiable certification links, named testimonials with photos), but no ready-to-use code, JSON-LD structured-data, or embed snippets are provided in-body — implementation is deferred to the reference.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and includes one verify step ("Verify all badges are genuine"), but there are no explicit validation checkpoints or a fix-and-reverify feedback loop, so checkpoints remain mostly implicit.

2 / 3

Progressive Disclosure

The body is a concise overview organized into clear sections and points to a single one-level-deep reference (references/rule.md, which exists) for implementation details and code examples, with clear signaling.

3 / 3

Total

9

/

12

Passed

Description

40%

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 distinctive and trigger-rich but structurally incomplete: it gives only "when to use" guidance and never says what the skill does, and the opening "Use when applies especially to" is grammatically malformed. Adding a leading capability statement (e.g., "Display trust signals on key conversion pages") would fix the main gap.

Suggestions

Add a concrete capability clause before the triggers, e.g., "Display trust signals (reviews, certifications, security badges) on key conversion pages. Use when...", so the description answers both 'what' and 'when'.

Repair the malformed opening "Use when applies especially to" to read "Use especially for" or lead with a third-person action verb.

Include the core vocabulary users would naturally say ("trust signals", "trust badges", "reviews", "certifications") alongside the domain contexts.

DimensionReasoningScore

Specificity

The description names the domain ("e-commerce checkouts, contact/lead forms, pricing pages, and YMYL") and an action ("auditing E-E-A-T or conversion optimization"), but never states the core capability (displaying/adding trust signals), so it names domain and some actions without being comprehensive.

2 / 3

Completeness

It provides two explicit "Use when..." trigger clauses but no statement of what the skill actually does, so the "what" half of the what/when pair is missing entirely.

1 / 3

Trigger Term Quality

It includes relevant terms a practitioner would say ("e-commerce checkouts", "pricing pages", "conversion optimization", "E-E-A-T", "YMYL"), but omits the most natural core vocabulary ("trust signals", "trust badges", "reviews", "certifications"), leaving common variations missing.

2 / 3

Distinctiveness Conflict Risk

The triggers (YMYL content, E-E-A-T auditing, conversion optimization on checkout/pricing/contact pages) define a narrow SEO/conversion niche that is unlikely to fire for unrelated skills.

3 / 3

Total

8

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.