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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/disclaimers/SKILL.md

Quality

Content

68%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.

The body is highly actionable — concrete disclaimer copy and a precise code-review procedure — and uses progressive disclosure well with a real one-level-deep reference. It loses points for re-explaining E-E-A-T concepts, omitting inline validation checkpoints for a batch audit, and some content duplication with the reference file.

Suggestions

Trim the intro paragraph and 'Explain' section to remove E-E-A-T/YMYL concept explanation that Claude already knows and that is duplicated in references/rule.md.

Add explicit validation checkpoints to the Fix workflow (e.g., 'Verify the disclaimer block renders before the first affiliate link or sensitive paragraph' and 'Confirm ARIA role/visual styling is present before approving the page').

De-duplicate the content-type guidance between SKILL.md's Fix list and rule.md's content-type table, pointing the body's per-type copy to the table for the single source of truth, and remove the empty '##' heading at line 12 of rule.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the intro paragraph and the 'Explain' section re-explain E-E-A-T/YMYL trust concepts Claude already knows, and that rationale is duplicated in references/rule.md — more than the 'minor instances' a 4 allows.	3 / 5
Actionability	Provides copy-paste-ready disclaimer text for medical, financial, legal, and affiliate content, a concrete placement rule, ARIA/visual guidance, and a concrete code-review scanning procedure (check disclaimer near top of <main>/<article>, affiliate disclosure before first <a> with a referral param) covering the common cases.	5 / 5
Workflow Clarity	The Fix section is a clear 7-step sequence, but the body has no inline validation checkpoints (e.g., verify the disclaimer renders before the first affiliate link), and the verification content lives only in references/rule.md; for a multi-page batch audit this caps the score at 3.	3 / 5
Progressive Disclosure	Well-organized sections with a single clearly-signaled, one-level-deep reference ('see references/rule.md') that genuinely exists, but the content-type guidance is duplicated between the body and rule.md and rule.md has a stray empty heading, leaving minor organization gaps short of a 5.	4 / 5
	Total	15 / 20 Passed

Description

78%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 specific, trigger-rich, and clearly scoped to a distinct niche, with an explicit 'Use when' clause. Its main limitation is incomplete topical coverage (legal, safety, and AI-generated content types are absent) and trigger framing that lists activities rather than user-utterance phrases.

Dimension	Reasoning	Score
Specificity	Names three concrete actions ('auditing YMYL content pages for trust signals,' 'generating disclaimer copy for medical or financial content,' 'reviewing affiliate disclosure requirements under FTC or ASA guidelines'), but omits legal/safety/AI-generated categories so coverage isn't comprehensive enough for a 5.	4 / 5
Completeness	Both 'what' (auditing/generating/reviewing disclaimers) and 'when' (explicit 'Use when...' clause) are present, but the 'when' is framed as activities rather than concrete user-trigger phrases, so it's not a 5.	4 / 5
Trigger Term Quality	Strong natural terms users would say ('disclaimer,' 'affiliate disclosure,' 'FTC,' 'ASA,' 'medical or financial content'), but missing common synonyms like 'sponsored content,' 'AI-generated,' and 'legal disclaimer,' keeping it below a 5.	4 / 5
Distinctiveness Conflict Risk	The YMYL-disclaimer + FTC/ASA affiliate-disclosure niche is distinct with clear triggers and minimal overlap with other skills; it fits the 'clear niche with minimal conflict risk' anchor better than the 'minor overlap' anchor at 4.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/disclaimers/SKILL.md
Commit: 30756a7

Reviewed: 25 days ago

Table of Contents

Discovery Implementation Validation

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.