CtrlK
BlogDocsLog inGet started
Tessl Logo

external-links

Use when auditing content pages for citation quality, suggesting authoritative sources to link for factual claims, or reviewing whether a page's external link attributes (nofollow, noopener) are correctly set.

63

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

Quality

Content

67%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-organized audit skill with actionable rel-attribute guidance, a concrete HTML example, and a clear Check/Fix/Code Review workflow that defers detail to a real references/rule.md file. Its main weakness is redundancy between the intro and the Explain section, which slightly inflates the token budget.

Suggestions

Merge or trim the 'Explain' section since it restates the intro's E-E-A-T and trust-signal rationale that Claude already knows, keeping the body lean.

Move or duplicate the references/rule.md pointer nearer the Quick Reference so the one-level-deep reference is clearly signaled per topic rather than buried at the end.

Add an explicit verify-and-recheck loop to the Code Review section (e.g. 'after adding links, re-crawl to confirm rel attributes and citation coverage') to strengthen the batch-audit feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient with clear sections, but the 'Explain' section restates the intro's E-E-A-T and trust-signal points and there is conceptual padding ('positive trust signal by Google', 'rank better for informational queries') that Claude already knows.

3 / 5

Actionability

Provides concrete rel values, a copy-paste HTML example, a numbered Fix sequence, and specific Code Review flags (e.g. zero-link pages in >500-word content), with only minor gaps such as no crawl/parse script.

4 / 5

Workflow Clarity

The Check → Fix → Code Review sequence is clear and the Code Review section supplies verification checkpoints (verify rel attrs, flag missing sponsored, count external links), so the batch-operation cap does not bind; only minor validation gaps remain.

4 / 5

Progressive Disclosure

Body is well-organized into Quick Reference, Check, Fix, Explain, and Code Review sections and defers full details to the one-level-deep references/rule.md (verified to exist), though the reference pointer is somewhat buried at the end rather than topic-mapped.

4 / 5

Total

15

/

20

Passed

Description

83%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 three concrete auditing actions, giving strong completeness and specificity. It is slightly held back by specialized, somewhat narrow trigger terms and minor overlap with adjacent SEO/citation skills.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions ('auditing content pages for citation quality', 'suggesting authoritative sources to link for factual claims', 'reviewing whether a page's external link attributes (nofollow, noopener) are correctly set'), but they are all review-oriented rather than a comprehensive multi-category action set.

4 / 5

Completeness

Opens with an explicit 'Use when' clause listing three concrete trigger phrases, while the actions inside those clauses define the 'what', clearly answering both what and when.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('citation quality', 'authoritative sources', 'factual claims', 'nofollow, noopener') but specialized and missing common synonyms a user might say such as plain 'external links'.

4 / 5

Distinctiveness Conflict Risk

Clear external-link/citation niche with distinct triggers (nofollow, noopener, citation quality), but minor overlap risk with a broader content-citations or general SEO skill.

4 / 5

Total

17

/

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.

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.