CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

63%

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

78%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 well-structured, mostly lean audit workflow: concrete checks, concrete fixes, and a clean hand-off to a single verified reference file. Its only weaknesses are mild redundancy between the intro and 'Explain' sections and the absence of explicit post-fix verification checkpoints.

DimensionReasoningScore

Conciseness

Lean checklist style with well-scoped Check/Fix sections; the only trimmable redundancy is that the intro paragraph and the 'Explain' section both restate the Quality Rater Guidelines / E-E-A-T rationale.

4 / 5

Actionability

Concrete, executable audit guidance ('Does it display author name and credentials?', "Add a 'reviewed by' note with the reviewer's credentials", 'Update... with a visible last-reviewed date') with minor gaps such as no example of what counts as an authoritative source.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and well-defined, and the Code Review section directs verifying final page output; it stops short of 5 because there are no explicit validation checkpoints for confirming fixes landed.

4 / 5

Progressive Disclosure

A short, well-sectioned body with a clearly signaled one-level-deep reference ('see references/rule.md', verified to exist) that holds the full implementation details.

5 / 5

Total

17

/

20

Passed

Description

47%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 trigger terms and a distinct YMYL niche, but it consists entirely of 'when' clauses with no statement of what the skill does, and the grammar is off ('Use when applies to'). It reads as a trigger list rather than a capability description.

Suggestions

Add a leading 'what' clause stating concrete capabilities, e.g. 'Identifies YMYL pages and audits their E-E-A-T trust signals (author credentials, citations, expert review, last-reviewed dates).' before the 'Use when' triggers.

Include common natural synonyms users would actually say — 'medical', 'financial', 'E-E-A-T', 'author credentials' — to widen trigger coverage from 4-level to 5-level.

Fix the ungrammatical opening 'Use when applies to any site...' to 'Use when the site covers...' or fold it into a single well-formed sentence.

DimensionReasoningScore

Specificity

Names the domains ('health, medicine, finance, law, safety, news... YMYL categories') but the actions ('auditing content quality', 'investigating') are minimal and generic, and the description never states what the skill concretely does (identify YMYL pages, assess E-E-A-T signals).

2 / 5

Completeness

Both sentences are 'Use when...' clauses, so only 'when' is present with no 'what' — matching the anchor 'Use when working with documents'. Not 3 because the implied what ('auditing') is vague, and not 4 because there is no statement of capability at all.

2 / 5

Trigger Term Quality

Good natural keyword coverage ('health, medicine, finance, law, safety, YMYL, content quality, underperforms'), but a few natural terms users would say are missing ('medical', 'financial', 'E-E-A-T', 'author credentials').

4 / 5

Distinctiveness Conflict Risk

YMYL is a clear niche with distinct domain triggers; minor overlap risk with general SEO-audit skills via 'investigating why high-quality-seeming content underperforms'.

4 / 5

Total

12

/

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