CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ymyl-detection

Use when applies to any site in health, medicine, finance, law, safety, news, or similar fields. Use when auditing content quality for sites in YMYL categories or investigating why high-quality-seeming content underperforms.

Quality

75%

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/ymyl-detection/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a lean, well-structured overview for a simple audit skill: concrete check questions and fix instructions, with detail correctly pushed to a single clearly referenced bundle file. Its weaknesses are redundant framing in the Quick Reference, a boilerplate 'Explain' section, and the absence of an explicit fix-verification step in the body.

Suggestions

Remove the Quick Reference bullet that duplicates the opening paragraph, and either cut the 'Explain' section or replace it with the actual explanation content.

Inline one or two small concrete examples (e.g. the reviewed-by footer or author-credentials HTML block) from references/rule.md so the Fix steps are immediately executable without loading the reference.

Add an explicit verification step after Fix, e.g. "Re-check the page for author byline, citations, and last-reviewed date before treating the rule as satisfied," referencing the verification guidance in references/rule.md.

DimensionReasoningScore

Conciseness

The body is brief overall, but the Quick Reference bullet "YMYL pages cover topics where inaccurate information could harm a user's health, safety, finances, or wellbeing" restates the opening paragraph almost verbatim, and the "Explain" section is boilerplate that describes what to explain rather than adding guidance. This matches anchor 3 (mostly efficient but could be tightened) rather than anchor 4, which requires only minor trims.

3 / 5

Actionability

The Check section poses concrete, answerable questions ("Does it display author name and credentials?", "Are claims supported by cited, authoritative sources?", "When was it last updated?") and the Fix section gives specific instructions ("Add author bylines with credentials", "Add a 'reviewed by' note with the reviewer's credentials", "Update outdated YMYL content with a visible last-reviewed date"). For an instruction-only skill this is mostly executable guidance; anchor 5's copy-paste-ready examples are deferred to references/rule.md rather than inlined.

4 / 5

Workflow Clarity

There is a clear Check-then-Fix sequence (audit pages for signals, then remediate with bylines, citations, and review dates), and the Code Review section instructs to "describe how to verify the final page output". However, no explicit validation checkpoint for the fixes is written in the body itself (verification details live only in references/rule.md), which keeps it at anchor 4 (most checkpoints present, minor validation gaps) rather than anchor 5.

4 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections and a clearly signaled one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and references/rule.md exists and delivers exactly that detail (HTML examples, checklist, schema, verification). This matches anchor 5: content appropriately split with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

70%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 has strong, explicit trigger guidance and good domain keyword coverage, but its statement of what the skill actually does is vague, and the opening phrase "Use when applies to any site" is grammatically malformed, hurting clarity. It is functional but below the quality of the good examples, which pair concrete capabilities with trigger phrases.

Suggestions

Lead with an explicit capability statement, e.g. "Identifies YMYL pages (health, finance, legal, safety, news) and flags missing E-E-A-T trust signals such as author credentials, citations, and review dates" before the 'Use when' clauses.

Fix the malformed opening phrase "Use when applies to any site" to a well-formed sentence such as "Use when the site covers health, medicine, finance, law, safety, or news topics".

Add common synonyms users would naturally say, such as "your money or your life", "E-E-A-T", and "trust signals", to strengthen trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("health, medicine, finance, law, safety, news") and gestures at two actions ("auditing content quality", "investigating why high-quality-seeming content underperforms"), but never states concrete capabilities like identifying YMYL pages or checking E-E-A-T signals. This matches anchor 3 (domain plus 1-2 actions, not comprehensive); anchor 4 requires several specific actions, and anchor 2 lacks even these action verbs.

3 / 5

Completeness

The 'when' is explicit and repeated ("Use when applies to any site in...", "Use when auditing content quality..."), and a 'what' is present ("auditing content quality for sites in YMYL categories") but vague — it never says the skill identifies YMYL pages or evaluates author credentials/citations. This sits between anchor 3 (clear what, weak when) and anchor 5 (both fully explicit), landing on anchor 4: both present, one could be more specific.

4 / 5

Trigger Term Quality

Good keyword coverage: "health, medicine, finance, law, safety, news", "YMYL", "auditing content quality", "underperforms" are terms a user auditing a site would plausibly say. A few natural terms are missing ("E-E-A-T", "your money or your life", "trust signals"), so it falls just short of anchor 5's comprehensive synonym coverage but clearly above anchor 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The YMYL framing is a clear niche with distinct trigger categories, so it is mostly distinguishable from generic SEO skills. Minor overlap risk remains with closely related skills like E-E-A-T or trust-signal audits ("auditing content quality" alone is broad), matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

15

/

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

thedaviddias/Front-End-Checklist

Path

skills/ymyl-detection/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.