CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

new-tab

Use when reviewing HTML or JSX for anchor elements with target='_blank' to verify rel='noopener noreferrer' is present.

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/new-tab/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.

A lean, well-sectioned body for a simple security check, with an appropriately signaled one-level reference file in the bundle. Deductions come from duplicated content between body and reference, time-sensitive version details in the main flow, generic Code Review boilerplate, and one incorrect inline ESLint rule name.

Suggestions

Drop the duplicated threat narrative and the browser-version bullet from the body — both are covered in references/rule.md — keeping the body to the rule, the check, and the fix.

Remove or tighten the generic "Code Review" section; server config, headers, and cookies are unrelated to an anchor-attribute check.

Correct the inline enforcement guidance: jsx-a11y/anchor-is-valid does not cover target="_blank"; the reference's react/jsx-no-target-blank is the accurate rule.

DimensionReasoningScore

Conciseness

Mostly efficient, but the opening attack narrative ("A malicious site opened via target='_blank' can use window.opener.location to silently redirect your original tab to a phishing page...") explains a reverse-tabnapping concept Claude already knows, time-sensitive version numbers ("Chrome 88+, Firefox 79+") sit in the main flow rather than a deprecated/old-patterns section, and the "Code Review" section reads as generic boilerplate. Not 2 because beyond these instances there is no real padding; not 4 because these unnecessary tokens are noticeable rather than minor.

3 / 5

Actionability

Concrete, executable guidance throughout: exact attribute values ("rel='noopener noreferrer' (or at minimum rel='noopener')"), a defined find-and-verify procedure, and named tooling ("ESLint rule `jsx-a11y/anchor-is-valid`"). Not 5 because no inline code or grep examples are provided (all deferred to the reference) and the named jsx-a11y rule does not actually govern target="_blank" (the reference file correctly uses react/jsx-no-target-blank); not 3 because the guidance is specific and directly executable, not pseudocode.

4 / 5

Workflow Clarity

The Check → Fix → Explain sequence is clear and unambiguous for a simple, non-destructive review task, and the Check step itself acts as validation ("Verify each one includes rel='noopener noreferrer'"). Not 5 because the appended "Code Review" section adds a vague fourth workflow ("Review server config, headers, forms, and integration points related to External Link Security") that muddies an otherwise single-purpose procedure.

4 / 5

Progressive Disclosure

The body is a genuine overview with a well-signaled, one-level-deep reference that exists in the bundle ("see `references/rule.md`"). Not 5 because the body's intro paragraph is duplicated verbatim in rule.md's "Why It Matters" section, and Quick Reference details (browser version behavior, ESLint enforcement) overlap content that belongs only in the reference file.

4 / 5

Total

15

/

20

Passed

Description

73%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, focused description with an explicit 'Use when...' trigger, third-person voice, and highly distinctive trigger terms. Its main limitation is breadth: it captures only the verification step, under-selling the fix, enforcement, and explanation capabilities the skill actually provides.

Suggestions

Broaden the 'what' clause to mention fixing violations and enforcing via ESLint, e.g. "...to verify rel='noopener noreferrer' is present, add it where missing, and configure lint enforcement".

Add common synonym trigger phrases such as "new tab" or "external links" so users who don't say "target='_blank'" still surface the skill.

DimensionReasoningScore

Specificity

The description "reviewing HTML or JSX for anchor elements with target='_blank' to verify rel='noopener noreferrer' is present" names the domain and one concrete action (verify the rel attribute). It is not 4 because only a single verification action is described — the fix, ESLint enforcement, and explanation the skill also performs are absent; it is not 2 because the action named is fully concrete, not generic.

3 / 5

Completeness

Both parts are explicit: the 'what' ("verify rel='noopener noreferrer' is present") and the 'when' ("Use when reviewing HTML or JSX for anchor elements with target='_blank'"). Not 5 because the 'what' covers only verification and omits the fix/enforcement actions the skill body delivers; not 3 because the 'when' clause is explicitly present with concrete trigger phrases.

4 / 5

Trigger Term Quality

Good keyword coverage with exact technical terms users would naturally say: "HTML", "JSX", "anchor elements", "target='_blank'", "rel='noopener noreferrer'". Not 5 because common natural variations such as "new tab", "external links", or "reverse tabnabbing" are missing; not 3 because the terms present are specific and match real user phrasing.

4 / 5

Distinctiveness Conflict Risk

The trigger pairing of "target='_blank'" with "rel='noopener noreferrer'" defines a clear niche that would not plausibly fire for any other skill, matching the minimal-conflict-risk anchor.

5 / 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/new-tab/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.