js-libraries

Use when auditing slow page loads, heavy assets, or rendering delays related to Use secure and up-to-date JS libraries. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

53%

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

The body is a lean, well-organized overview that delegates executable detail cleanly to a single one-level-deep reference, which is good progressive disclosure. Its weaknesses are redundancy across the Quick Reference and Check/Fix/Explain sections, no executable commands in the body itself, and no explicit validation feedback loop for dependency updates.

Suggestions

Surface at least one concrete command inline (e.g. `npm audit`) in the Check section so the body is actionable without requiring the reader to open the reference.

Add an explicit validation checkpoint after Fix — e.g. re-run `npm audit` (or Lighthouse/bundle-size measurement) to confirm the vulnerability or bloat is resolved before considering the task done.

Collapse the overlapping Quick Reference bullets and the Check/Fix/Explain sections into one set of concrete steps to remove the redundancy.

Dimension	Reasoning	Score
Conciseness	The body is short and assumes Claude's competence, but the Quick Reference bullets overlap with the Check/Fix/Explain sections (e.g. "audit dependencies for known security vulnerabilities" restated twice), so it could be tightened by consolidating.	2 / 3
Actionability	Guidance like "Update vulnerable libraries to secure versions" and "Check the project's JavaScript dependencies for known vulnerabilities" is directionally concrete but the body itself contains no executable commands or code — all of that is deferred to references/rule.md — so it is incomplete on its own.	2 / 3
Workflow Clarity	The Check → Fix → Explain → Code Review sections imply a loose sequence and the Code Review step asks to "describe the measurement method used to confirm the issue", but there is no explicit validate-then-retry feedback loop for what is a batch/destructive-ish dependency-update task.	2 / 3
Progressive Disclosure	The body is a concise overview with clear sections and a single, well-signaled one-level-deep reference — "see `references/rule.md`" (verified to exist) — so detail is appropriately split and navigation is easy.	3 / 3
	Total	9 / 12 Passed

Description

50%

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 malformed — a template-style doubling ("related to Use secure and up-to-date JS libraries") jammed into a performance-audit trigger — leaving the skill's true purpose unclear and its triggers aimed at the wrong problem. It does carry an explicit "Use when..." clause and some concrete tool names, but the mismatch and garbling keep every dimension at a middling level.

Suggestions

Rewrite the description to lead with the skill's real purpose, e.g. "Audit JavaScript dependencies for known vulnerabilities and replace heavy libraries with lightweight alternatives. Use when the user mentions outdated or vulnerable libraries, npm audit, bundle size, or dependency security."

Remove the duplicated/garbled "related to Use secure and up-to-date JS libraries" fragment so the sentence parses as a single coherent trigger clause.

Align trigger terms with the skill's domain (outdated/vulnerable libraries, npm audit, Snyk, dependency security) instead of performance-audit terms (slow page loads, rendering delays) that would cause it to fire for the wrong skill.

Dimension	Reasoning	Score
Specificity	Phrases like "auditing slow page loads, heavy assets, or rendering delays" and "Verify the actual bottleneck in DevTools, Lighthouse, or field data" name several concrete actions, but they describe performance auditing rather than the skill's actual purpose (JS library security/updating), so they are not cleanly comprehensive.	2 / 3
Completeness	It includes an explicit "Use when..." trigger (the when), but the what is garbled by the doubled phrase "related to Use secure and up-to-date JS libraries", leaving the skill's actual capability unclear rather than cleanly stated.	2 / 3
Trigger Term Quality	Terms such as "slow page loads", "heavy assets", "rendering delays", "DevTools", and "Lighthouse" are natural performance-audit keywords, but they are mismatched to this skill — a user needing JS-library security would say "outdated/vulnerable libraries" or "npm audit", which are absent.	2 / 3
Distinctiveness Conflict Risk	The description leads with generic performance-audit triggers (slow loads, heavy assets, rendering delays) that overlap with general performance-auditing skills, while the library-security niche is buried and awkwardly phrased, raising conflict risk.	2 / 3
	Total	8 / 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/js-libraries/SKILL.md
Commit: 48405aa

Reviewed: about 10 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.