CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

duplicate-js

Use when auditing slow page loads, heavy assets, or rendering delays related to Remove duplicate JavaScript libraries. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

68%

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/duplicate-js/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 lean, well-sectioned overview that correctly defers implementation detail to a single, real, one-level-deep reference file. However, the body itself contains no executable commands or code, and the workflow lacks a post-fix validation checkpoint, so Claude must open the reference before it can act.

Suggestions

Inline one or two concrete commands in the Check/Fix sections (e.g., `npm ls <package>`, `pnpm why <package>`, or the package.json `overrides` snippet) instead of deferring all executable detail to references/rule.md.

Add an explicit post-fix validation step to the workflow, such as re-running Lighthouse or the bundle analyzer to confirm the duplicate is gone and the targeted metric improved.

Trim the intro sentence explaining why duplicate libraries are harmful (Claude already knows this) and tighten the generic Code Review boilerplate that repeats the rule title.

DimensionReasoningScore

Conciseness

The ~35-line body is sectioned and lean ('Detect and remove multiple versions of the same library'), with only minor over-explanation: the intro 'Duplicate libraries increase bundle size and memory usage, and can lead to unexpected behavior or conflicts' explains a concept Claude already knows, and the Code Review section awkwardly repeats the rule title. Not 5 because of that known-concept intro and the templated Code Review boilerplate; not 3 because padding is minor, not 'several unnecessary explanations'.

4 / 5

Actionability

The body gives only high-level hints — 'Identify duplicate JavaScript libraries ... using Lighthouse or bundle analysis tools' and 'Consolidate dependencies to use a single version' — with no commands, code, or specific steps; all executable detail (npm ls, overrides, dedupe) is deferred to references/rule.md. Matches anchor 2 ('high-level hints but missing the specific steps'), not 3 (no partially-complete concrete guidance exists in the body) and not 1 (specific tools and concrete tasks are named rather than pure abstraction).

2 / 5

Workflow Clarity

A recognizable Check → Fix sequence is present and the Code Review section asks to 'describe the measurement method used to confirm the issue', but that only confirms the problem pre-fix; there is no post-fix validation checkpoint in the body (e.g., re-run Lighthouse to confirm improvement). Matches anchor 3 ('sequence present but checkpoints missing or implicit'), not 4 (the validation gap is more than minor) and not 2 (steps are defined per section, not poorly defined).

3 / 5

Progressive Disclosure

The body is a concise overview with clear sections and a well-signaled one-level-deep pointer — 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and the referenced file exists, delivers the promised content (npm/pnpm commands, package.json overrides example, best practices, verification), and introduces no further nesting. Matches anchor 5 ('clear overview with well-signaled one-level-deep references'); not 4 since the split and navigation have no notable organization gaps.

5 / 5

Total

14

/

20

Passed

Description

66%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 has an explicit, natural 'Use when' trigger set and names concrete verification tools, but it embeds the skill's actual capability only indirectly through the rule title and opens with generic performance triggers that overlap with sibling performance skills. It is serviceable but understates what the skill does.

Suggestions

State the core capability directly (e.g., 'Detect and consolidate duplicate JavaScript libraries to reduce bundle size') instead of embedding the rule title in 'related to Remove duplicate JavaScript libraries'.

Add distinguishing trigger terms such as 'duplicate packages', 'bundle size', or 'npm dedupe' so it does not compete with sibling performance-audit skills that share the same 'slow page loads' opening.

Lead with the capability statement and place the verification guidance ('Verify the actual bottleneck in DevTools, Lighthouse, or field data') after it, so the 'what' is direct rather than implied.

DimensionReasoningScore

Specificity

Names the domain ('Remove duplicate JavaScript libraries') and 1–2 concrete actions ('auditing slow page loads', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data'), but the skill's core capabilities — detecting and consolidating duplicates — are never stated as actions. Matches anchor 3 ('domain and 1-2 concrete actions, but not comprehensive'), not 4 ('several specific actions') because the primary capabilities are missing, and not 2 because the stated actions are concrete rather than generic.

3 / 5

Completeness

The 'when' is explicit and specific ('Use when auditing slow page loads, heavy assets, or rendering delays'), and a 'what' is present ('Verify the actual bottleneck ... before recommending changes'), but the core capability is only implied via the awkward title embedding 'related to Remove duplicate JavaScript libraries' rather than a direct statement. Falls between anchor 4 (both present, one could be stronger) and anchor 5 (both clearly and directly stated) — the indirect 'what' keeps it at 4; not 3 because the 'when' clause is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Good natural phrases users would actually say: 'slow page loads', 'heavy assets', 'rendering delays', plus tool names 'DevTools', 'Lighthouse'. Missing common variations such as 'bundle size', 'duplicate packages', 'npm dedupe', or 'page speed'. Matches anchor 4 ('good keyword coverage; a few natural terms missing'), not 5 (no synonyms/extensions coverage) and not 3 (the terms present are natural, not merely relevant).

4 / 5

Distinctiveness Conflict Risk

'Remove duplicate JavaScript libraries' names a specific niche, but the leading triggers 'slow page loads, heavy assets, or rendering delays' are generic performance-audit language that would overlap with any sibling frontend-performance skill sharing this template. Matches anchor 3 ('somewhat specific but could still overlap with similar skills'), not 4 (overlap risk is more than minor given the shared generic triggers) and not 2 (the duplicate-JS topic does distinguish it from unrelated skills).

3 / 5

Total

14

/

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/duplicate-js/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.