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.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, actionable SEO audit skill with clean progressive disclosure and a verified reference file. It is held back by redundant concept explanation and a workflow that lacks an explicit validation feedback loop tying the sections together.

Suggestions

Trim the intro paragraph and 'Explain' section — Claude already knows E-E-A-T and that outbound links are a trust signal — and remove the overlap between the intro and the first Quick Reference bullet to improve conciseness.

Convert the parallel Check / Fix / Code Review sections into one gated sequence with an explicit 'verify after fixing, re-run the audit if issues remain' feedback loop to raise workflow clarity.

Add one concrete mechanism for finding external links (e.g., a grep/selector snippet) so the audit step is as executable as the fix example.

DimensionReasoningScore

Conciseness

The opening paragraph and the 'Explain' section restate SEO/E-E-A-T trust-signal concepts Claude already knows, and the first Quick Reference bullet overlaps the intro; it is mostly efficient but includes unnecessary explanation that could be tightened.

2 / 3

Actionability

It gives concrete rel attribute values, a complete copy-paste HTML before/after example with a real URL, and explicit check/fix steps; as an instruction-only content skill its guidance is directly actionable, so lack of a runnable script is not penalized.

3 / 3

Workflow Clarity

Check, Fix, and Code Review sections are sequenced and include a checklist and a verification section, but there is no explicit gated feedback loop (validate → fix → retry) and the checkpoints remain implicit across parallel sections.

2 / 3

Progressive Disclosure

The body is a concise overview organized into clear sections, with a single clearly-signaled one-level reference ('see references/rule.md') that exists on disk, avoiding nested or monolithic structure.

3 / 3

Total

10

/

12

Passed

Description

100%

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 well-crafted description: specific, third-person, with an explicit 'Use when' trigger and natural keywords that distinguish it from neighboring SEO skills. It cleanly answers both what the skill does and when to use it.

DimensionReasoningScore

Specificity

The description lists three concrete actions — 'auditing content pages for citation quality', 'suggesting authoritative sources to link for factual claims', and 'reviewing whether a page's external link attributes (nofollow, noopener) are correctly set' — matching the anchor for multiple specific concrete actions, in third-person gerund voice.

3 / 3

Completeness

It opens with an explicit 'Use when ...' clause and states both what the skill does (audit citations, suggest sources, review link attributes) and when to invoke it, satisfying the what-and-when requirement.

3 / 3

Trigger Term Quality

It surfaces natural terms a user would say — 'citation quality', 'authoritative sources', 'external link attributes', 'nofollow, noopener' — giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

The external-links / citation-quality niche with specific rel-attribute triggers is clearly distinguishable and unlikely to fire for unrelated SEO skills.

3 / 3

Total

12

/

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.