article-links

Use when auditing metadata, crawlability, structured data, or indexability related to Optimize article link density. Verify the rendered HTML and HTTP response rather than relying only on source files.

Quality

61%

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-links/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 concise, well-structured, and cleanly delegates detail to a real references/rule.md bundle file with good verification guidance. Its main weakness is actionability inside SKILL.md itself, which gives quantitative targets but no inline executable code or commands.

Suggestions

Add a short inline executable snippet (e.g., a grep/regex or DOM check to count internal vs external anchors) so the skill is actionable without opening the reference.

Move the 'A natural link profile...' opening sentence into the reference since it restates widely known context.

Make the pointer to references/rule.md more navigable by listing the sub-sections (Code Example, Verification) it contains.

Dimension	Reasoning	Score
Conciseness	The body is short and well-sectioned (Quick Reference, Check, Fix, Explain, Code Review) with little padding, though lines like the opening paragraph and 'A natural link profile within articles establishes authority...' restate context Claude largely already knows, leaving minor trimmable excess.	4 / 5
Actionability	It gives numeric, concrete targets ('Add 2-3 internal links... 1-2 external links') but provides no executable code or commands in the SKILL.md body itself; the actionable code lives only in the referenced rule.md, matching the anchor of some concrete guidance that is incomplete.	3 / 5
Workflow Clarity	The Check -> Fix -> Explain -> Code Review sections form a clear sequence with a verification emphasis in Code Review ('verify the final page output'), and the referenced rule.md adds Automated/Manual verification checkpoints, leaving only minor gaps in the inline workflow.	4 / 5
Progressive Disclosure	The SKILL.md is a clean overview that signals one-level-deep references to the real references/rule.md bundle file (which exists), with content appropriately split between overview and reference; minor gaps as the reference is signaled generically rather than with multiple navigable sub-topics.	4 / 5
	Total	15 / 20 Passed

Description

57%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 clearly states a trigger ('Use when auditing...') and concrete verification actions, giving it solid completeness, but its actions are not fully comprehensive and the trigger terms lean on technical jargon over natural user phrasing. The broad SEO scope creates some overlap risk with sibling SEO skills.

Suggestions

Add concrete natural trigger phrases users would say (e.g., 'when the user mentions link density, internal/external link balance, or article SEO') rather than only technical terms.

Sharpen the 'what' by listing specific actions like 'count internal vs external links in rendered article HTML and flag missing authoritative citations'.

Narrow the scope to article link density specifically so it is distinguishable from generic metadata/crawlability SEO skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('auditing metadata, crawlability, structured data, or indexability') plus a concrete action ('Verify the rendered HTML and HTTP response'), but the overall action framing ('Use when auditing...') is generic and not comprehensive, matching the anchor that lists domain plus 1-2 concrete actions.	3 / 5
Completeness	It answers both what (auditing metadata/crawlability/structured data/indexability and verifying rendered HTML/HTTP response) and when ('Use when auditing...'), though the 'when' trigger is somewhat general and could be more explicit.	4 / 5
Trigger Term Quality	It includes relevant keywords ('metadata', 'crawlability', 'structured data', 'indexability', 'rendered HTML', 'HTTP response') but lacks common natural user phrases and synonyms users would actually say, fitting the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	The phrase 'auditing metadata, crawlability, structured data, or indexability' is fairly broad SEO territory that could overlap with other SEO skills, though the rendered-HTML/HTTP-response angle adds some distinctiveness.	3 / 5
	Total	13 / 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-links/SKILL.md
Commit: 30756a7

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