CtrlK
BlogDocsLog inGet started
Tessl Logo

disclaimers

Use when auditing YMYL content pages for trust signals, generating disclaimer copy for medical or financial content, or reviewing affiliate disclosure requirements under FTC or ASA guidelines.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is actionable and well-structured with a clean one-level reference, but it could be tightened by de-duplicating the E-E-A-T explanation across the intro, Quick Reference, and Explain sections.

Suggestions

Consolidate the E-E-A-T/YMYL rationale: explain it once (e.g. in the Explain section) and let the intro and Quick Reference reference it without restating the framework.

Trim the opening paragraph's background on what YMYL pages are, since Claude already knows this, and keep only the trust-signal consequence relevant to the task.

DimensionReasoningScore

Conciseness

Mostly efficient, but the E-E-A-T/YMYL rationale is repeated across the intro, Quick Reference, and Explain sections, and some background ('held to the highest trust standards') is concepts Claude already knows.

2 / 3

Actionability

Provides copy-paste-ready disclaimer text for medical, financial, legal, and affiliate content, plus concrete detection guidance (check for a disclaimer element near the top of <main>/<article>, verify FTC disclosure before the first <a> with a referral parameter).

3 / 3

Workflow Clarity

A single-purpose skill with a clear Check → Fix sequence (numbered 1–7) and a Code Review section that functions as verification; no destructive/batch operations so no feedback-loop cap applies.

3 / 3

Progressive Disclosure

Well-organized overview sections with a single, clearly signaled one-level-deep reference ('see references/rule.md') that exists as a real file holding the detailed HTML examples.

3 / 3

Total

11

/

12

Passed

Description

100%

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

A well-constructed description with an explicit trigger clause, several concrete capabilities, and natural user-facing terms within a distinct niche. No material weaknesses to address.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'auditing YMYL content pages for trust signals', 'generating disclaimer copy for medical or financial content', and 'reviewing affiliate disclosure requirements under FTC or ASA guidelines' — rather than vague language.

3 / 3

Completeness

Opens with an explicit 'Use when' clause and answers both what it does (audit/generate/review disclaimers) and when to use it (YMYL, medical/financial content, affiliate disclosures).

3 / 3

Trigger Term Quality

Covers natural terms a user would say ('disclaimer copy', 'medical or financial content', 'affiliate disclosure requirements', 'FTC or ASA guidelines'); the 'YMYL' and 'trust signals' jargon is offset by these plain-language triggers.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (regulatory disclaimers for sensitive/affiliate content under FTC/ASA) with triggers unlikely to fire for unrelated SEO skills.

3 / 3

Total

12

/

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.