CtrlK
BlogDocsLog inGet started
Tessl Logo

new-tab

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

66

Quality

80%

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

70%

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

The content is well-structured with clear progressive disclosure to a single real reference file and an unambiguous review workflow. The two weak spots are an unnecessary conceptual opener that restates knowledge Claude already has and the absence of in-body executable code examples (delegated to the reference).

Suggestions

Remove or condense the opening paragraph restating the reverse-tabnapping attack; Claude already knows this concept, so start directly with the actionable Quick Reference bullets.

Add one minimal in-body HTML/JSX before-and-after code snippet (vulnerable vs. rel=\"noopener noreferrer\") so the fix is copy-paste ready without forcing a jump to the reference.

Add an explicit verification checkpoint in the Check or Fix section (e.g., re-grep after edits to confirm no target=\"_blank\" links remain without the attribute) to close the find→fix→verify loop.

DimensionReasoningScore

Conciseness

The body is mostly lean — terse bullets and short imperative sections that offload detail to references/rule.md — but opens by restating the reverse-tabnapping attack ('A malicious site opened via target=\"_blank\" can use window.opener.location to silently redirect...'), a concept Claude already knows and could be trimmed.

2 / 3

Actionability

It gives concrete guidance — the exact attribute string rel=\"noopener noreferrer\" and named ESLint rules (jsx-a11y/anchor-is-valid, eslint-plugin-security) — but keeps executable code examples out of the body, so the in-body guidance is concrete yet incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence clearly orders find → verify → flag → fix for a single-purpose review task, and the guideline allowing simple unambiguous tasks to score 3 applies; the action is unambiguous.

3 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference to references/rule.md (a verified real file) for code examples and framework guidance, matching the well-signaled one-level-deep anchor.

3 / 3

Total

10

/

12

Passed

Description

90%

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 strong: it has an explicit 'Use when' trigger, natural keyword coverage, and a clearly distinct niche. Its only limitation is that it names a single verification capability rather than enumerating multiple concrete actions, capping specificity at 2.

DimensionReasoningScore

Specificity

Names a concrete domain (anchor elements with target='_blank') and a specific verification action, but lists only a single capability rather than multiple distinct actions, matching the 'names domain and some actions' anchor rather than the comprehensive score-3 example.

2 / 3

Completeness

Explicitly answers both 'what' (verify rel='noopener noreferrer' is present) and 'when' with an explicit 'Use when reviewing HTML or JSX for anchor elements with target=\"_blank\"' trigger clause, matching the score-3 example exactly.

3 / 3

Trigger Term Quality

Includes natural terms developers actually say — 'HTML', 'JSX', 'anchor elements', and "target='_blank'" — giving good coverage of the phrasings a user would naturally use when requesting this check.

3 / 3

Distinctiveness Conflict Risk

The reverse-tabnapping / external-link niche is highly specific, anchored on target='_blank' plus the noopener/noreferrer attribute, making it unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

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.