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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/duplicate-js/SKILL.md

Quality

Content

57%

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

A well-structured, appropriately split skill body with clean progressive disclosure to a real reference file. It is held back by mostly abstract guidance in the body (no concrete commands/code) and the absence of an explicit post-fix validation checkpoint.

Suggestions

Add at least one concrete command or code snippet inline (e.g., an npm/pnpm dedup command or a bundle-analyzer invocation) so the body is actionable without requiring the reference.

Insert an explicit validation step after Fix, such as re-running the bundle analysis to confirm duplicate versions are gone before reporting completion.

Trim the generic opening sentence about bundle size and memory usage, which Claude already knows, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the opening 'Duplicate libraries increase bundle size and memory usage, and can lead to unexpected behavior or conflicts' restates basic knowledge Claude already has, and Quick Reference overlaps with the Check/Fix sections, so it does not fully earn the top anchor.	2 / 3
Actionability	It names real tools (Lighthouse, bundle analysis tools) and points to references/rule.md for examples, but the body itself gives only abstract direction ('Consolidate dependencies to use a single version') with no executable commands or code, fitting the incomplete-guidance anchor.	2 / 3
Workflow Clarity	Check, Fix, and Explain form a loose sequence, but there is no explicit validation/re-checkpoint after the fix; the only verification hint is in Code Review ('measurement method used to confirm the issue'), leaving checkpoints implicit rather than explicit.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview and clearly signals a single one-level-deep reference ('For full implementation details ... see references/rule.md'), which is a real file, matching the well-signaled one-level-deep reference anchor.	3 / 3
	Total	9 / 12 Passed

Description

92%

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, explicit-trigger description that clearly conveys what the skill does and when to use it, with good natural-language trigger terms. Its main weakness is that the leading symptom triggers are broad enough to conflict with sibling performance skills.

Suggestions

Lead with the distinctive trigger (e.g., 'Use when you suspect multiple versions of the same JS library are bundled') before the generic performance symptoms to reduce overlap with other performance skills.

Tighten 'related to Remove duplicate JavaScript libraries' so it reads as a natural user phrase rather than a rule title splice.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data', and 'recommending changes', matching the score-3 anchor for several specific concrete actions.	3 / 3
Completeness	An explicit 'Use when ...' clause answers when to invoke it, and 'Verify the actual bottleneck ... before recommending changes' answers what it does, satisfying both halves at the top anchor.	3 / 3
Trigger Term Quality	Includes natural performance terms a user would say ('slow page loads', 'heavy assets', 'rendering delays') plus named tooling (DevTools, Lighthouse), giving good coverage rather than just technical jargon.	3 / 3
Distinctiveness Conflict Risk	The qualifier 'related to Remove duplicate JavaScript libraries' narrows the niche, but the leading trigger symptoms (slow page loads, heavy assets, rendering delays) are generic and would overlap with other performance skills, so it stays at 2 rather than 3.	2 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/duplicate-js/SKILL.md
Commit: 48405aa

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.