article

Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid Article structured data. Verify the rendered HTML and HTTP response rather than relying only on source files.

Quality

67%

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/article/SKILL.md

Quality

Content

65%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 content is a well-organized, lean overview that uses progressive disclosure effectively by offloading details to a real references/rule.md file. It is weakest on actionability and workflow clarity because the body itself lacks executable code and explicit validation checkpoints, relying on the reference for both.

Suggestions

Inline a minimal copy-paste-ready JSON-LD script block in the Fix section so the body is actionable without opening the reference.

Add an explicit verification checkpoint in the workflow (e.g., 'After adding the JSON-LD, re-check rendered HTML and validate with Google's Rich Results Test') to close the validation loop in the body.

Trim the introductory sentence about rich results and CTR, which explains benefits Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is lean with short, focused sections and a useful Quick Reference; the only mild over-explanation is the intro sentence about rich results and CTR that assumes Claude lacks knowledge it already has.	4 / 5
Actionability	The Quick Reference names concrete types and required properties and the Fix section gives direction, but the body itself contains no executable code (the JSON-LD example lives only in references/rule.md), leaving the inline guidance incomplete.	3 / 5
Workflow Clarity	A clear Check/Fix/Explain/Code Review sequence is present, but validation checkpoints and a fix-then-revalidate feedback loop are implicit in the body and delegated to the reference, matching the validation-gaps anchor.	3 / 5
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md'), which exists and holds the implementation details, with well-organized sections and easy navigation.	5 / 5
	Total	15 / 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 is well-structured with an explicit 'Use when' trigger and concrete verification guidance, scoring well on completeness and trigger terms. It is slightly limited on specificity and has minor overlap risk with related SEO auditing skills.

Dimension	Reasoning	Score
Specificity	Names the SEO domain and a couple of concrete actions ('auditing metadata, crawlability, structured data, or indexability' and 'Verify the rendered HTML and HTTP response'), but does not enumerate several specific actions, fitting the 1-2 concrete actions anchor rather than comprehensive coverage.	3 / 5
Completeness	Explicitly provides both a 'when' ('Use when auditing...') and a 'what' ('Verify the rendered HTML and HTTP response rather than relying only on source files'), but the 'what' is somewhat narrow and the rule title is awkwardly embedded, so it stops short of the fully concrete trigger-phrasing anchor.	4 / 5
Trigger Term Quality	Includes natural SEO-oriented terms a user would say ('metadata', 'crawlability', 'structured data', 'indexability', 'Article structured data') with good coverage, though a few common synonyms/extensions are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped specifically to 'Implement valid Article structured data' giving it a clear niche, though the broad audit triggers (metadata, crawlability, indexability) create minor overlap risk with sibling SEO skills.	4 / 5
	Total	15 / 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/article/SKILL.md
Commit: 30756a7

Reviewed: 20 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.