CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

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/article-links/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a clean overview that correctly offloads detail to a single real reference file. Its main weaknesses are a conceptual opening paragraph and the lack of explicit verification steps inline.

Suggestions

Remove or shorten the introductory 'A natural link profile...' paragraph, which states SEO basics Claude already knows.

Add an inline verification checkpoint (e.g. confirm link counts in rendered HTML and re-check with a crawler) rather than only deferring to references/rule.md.

Make the Check step concrete with the same 2-3 / 1-2 thresholds used in Fix instead of 'a sufficient number'.

DimensionReasoningScore

Conciseness

The section bodies (Quick Reference, Check, Fix, Explain, Code Review) are tight, but the opening paragraph ('A natural link profile within articles establishes authority, improves site crawlability...') explains SEO concepts Claude already knows and could be trimmed.

2 / 3

Actionability

Gives some concrete guidance ('Add 2-3 internal links to related content and 1-2 external links to authoritative sources'), but the Check step is vague ('a sufficient number of relevant internal and external links') and the executable HTML example lives only in the reference file.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is present, but there are no explicit validation checkpoints or feedback loops in the body; verification guidance is deferred to the reference.

2 / 3

Progressive Disclosure

The body is a concise overview with a clearly signaled one-level-deep pointer ('see references/rule.md') to the full implementation details, and rule.md exists as a real file.

3 / 3

Total

9

/

12

Passed

Description

82%

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-formed with an explicit 'Use when' trigger and natural SEO keywords, covering both what and when. It is somewhat held back by broad audit vocabulary that could overlap with sibling SEO skills.

Suggestions

Tie the trigger more tightly to the article-links rule (e.g. 'when checking internal/external link density in article body content') to reduce overlap with other SEO audit skills.

Replace generic audit verbs with the specific concrete actions this skill performs (count internal vs external links, flag missing authoritative citations).

DimensionReasoningScore

Specificity

Names the SEO domain and a couple of concrete actions ('auditing metadata, crawlability, structured data, or indexability', 'Verify the rendered HTML and HTTP response'), but the actions are broad audit categories rather than a comprehensive list of distinct concrete operations.

2 / 3

Completeness

Explicitly states what the skill does (audit/verify metadata, crawlability, structured data, indexability) and when to use it via a clear 'Use when...' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural SEO terms a user would say ('metadata', 'crawlability', 'structured data', 'indexability', 'rendered HTML', 'HTTP response'), giving good coverage of likely request phrasing.

3 / 3

Distinctiveness Conflict Risk

Tying it to 'Optimize article link density' gives it a niche, but the trigger terms (metadata, crawlability, structured data, indexability) are generic across many SEO skills and could cause overlap.

2 / 3

Total

10

/

12

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.

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