CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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

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

A well-structured overview with actionable audit criteria and a proper reference split. Its weaknesses are redundancy — the same SEO rationale appears three times and Code Review duplicates the Check criteria — and the lack of an explicit post-fix re-verification step.

Suggestions

State the trust-signal rationale once (e.g., keep the intro sentence, drop the duplicate Quick Reference bullet and condense the Explain section) to remove the repeated rationale.

Merge the Check and Code Review sections, or reframe Code Review as an explicit post-fix verification pass so it does not duplicate the audit criteria.

Move the before/after HTML example into the body only once and rely on references/rule.md for the remaining code examples, trimming duplicated detail.

DimensionReasoningScore

Conciseness

Mostly efficient, but the trust-signal rationale is repeated three times (intro, the Quick Reference bullet 'External links to reputable sites do not hurt your SEO; Google treats them as a trust signal', and the Explain section), and the Code Review section restates the Check section's three checks nearly verbatim. These duplications go beyond the 'minor trim instances' that would justify a 4.

3 / 5

Actionability

Concrete, executable guidance throughout: five numbered Fix steps, specific criteria ('government sites, peer-reviewed research, official documentation', '>500 words'), and a complete before/after HTML example with rel="noopener noreferrer". Not 5 because no parsing/crawling tooling is given and the sponsored-link HTML example lives only in the reference file.

4 / 5

Workflow Clarity

A clear Check -> Fix -> Explain -> Code Review sequence, with the Code Review section serving as verification ('Verify each external link has rel="noopener noreferrer". Flag paid/affiliate links missing rel="sponsored". Count external links per page'). Minor gap: no explicit re-check loop after applying fixes, and the section order buries verification after the Explain rationale.

4 / 5

Progressive Disclosure

The body is a concise, well-organized overview (~40 lines) and clearly signals a one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' (the file exists and contains the code examples and detailed tables). Content is appropriately split between overview and reference with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

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

A strong, trigger-first description that names three concrete capabilities with specific attribute terms. Its main limitation is the fused what/when construction and slightly incomplete coverage of the rel attribute space it actually governs.

Suggestions

Add 'sponsored' alongside 'nofollow, noopener' in the attribute list so the description covers the full scope the skill body handles.

Include a couple of common trigger synonyms such as 'outbound links' or 'link audit' to broaden natural-keyword matching.

DimensionReasoningScore

Specificity

Lists 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') with named attributes. Not 5 because coverage has a minor gap: the skill also handles rel="sponsored"/UGC attributes, which the description omits.

4 / 5

Completeness

The explicit 'Use when auditing... suggesting... or reviewing...' clause answers 'when' with three concrete trigger scenarios, and the actions themselves state the 'what'. Not 5 because what and when are fused into a single sentence rather than both clearly and separately explicit, as in the anchor-5 example.

4 / 5

Trigger Term Quality

Good natural-term coverage: 'citation quality', 'authoritative sources', 'factual claims', 'external link', 'nofollow', 'noopener'. A few common variations are missing, such as 'outbound links', 'rel attributes', and 'sponsored links', which keeps it below 5.

4 / 5

Distinctiveness Conflict Risk

The niche (external-link auditing and rel attribute review) is distinct and unlikely to trigger for unrelated skills. Minor overlap risk remains with closely related SEO content skills such as a general citations or trust-signals rule, so it does not reach the minimal-conflict bar of 5.

4 / 5

Total

16

/

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

Path

skills/external-links/SKILL.md

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.