find-npm-packages

Use when you need to find the 2-3 most popular and well-maintained npm packages relevant to a frontend checklist rule, validate they meet quality thresholds, and add them to the rule's frontmatter.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/find-npm-packages/SKILL.md

Quality

Content

81%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 well-structured, highly actionable instruction-only skill: concrete commands, exact paths, explicit quality thresholds, and validation feedback loops for a batch operation. The main improvements are removing the redundant threshold restatement in 'What NOT to do' and making the candidate-search step more concrete.

Suggestions

Consolidate the 'What NOT to do' section with the thresholds table to remove near-duplicate statements of the same criteria.

Replace Step 2's high-level search guidance with a concrete, executable search command or an explicit keyword-derivation recipe from the rule's content.

Dimension	Reasoning	Score
Conciseness	Mostly lean with no explanations of concepts Claude already knows, but the 'What NOT to do' section almost fully restates the mandatory thresholds table ('Do not add packages with <10k weekly downloads', 'Do not add packages last published >18 months ago'), which could be trimmed.	4 / 5
Actionability	Provides executable curl/jq commands with exact registry endpoints, exact rule file paths, precise frontmatter placement ('after tools: and before resources:'), and a runnable pnpm validation command; the only gap is Step 2's high-level search guidance ('Use https://www.npmjs.com/search?q={keywords} and knowledge of the ecosystem') rather than a copy-paste-ready command.	4 / 5
Workflow Clarity	Five clearly sequenced steps with explicit per-candidate validation (Step 3: 'Reject any below threshold') and a post-edit feedback loop for a batch operation ('Run the validation script... If any package fails, either remove it or replace it with a better alternative'), matching the strongest anchor including error recovery.	5 / 5
Progressive Disclosure	No bundle files exist and the ~115-line single-purpose skill is organized into focused, well-signaled sections with everything appropriately inline; minor organization gaps (the duplicated threshold restatement and example section could be consolidated) keep it below the top anchor.	4 / 5
	Total	17 / 20 Passed

Description

75%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 description that names concrete actions, a specific niche, and an explicit use-when clause. Main weaknesses are the second-person voice, a when-clause that mirrors the what instead of adding trigger phrases, and missing common synonyms like 'dependencies' or 'libraries'.

Suggestions

Rewrite in third person ('Use when finding...' instead of 'Use when you need to find...') to match the voice guideline.

Add distinct trigger phrases to the when-clause, e.g. 'when the user asks to add npm packages or dependencies to a checklist rule'.

Include common synonyms such as 'dependencies', 'libraries', or 'package quality' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('find the 2-3 most popular and well-maintained npm packages', 'validate they meet quality thresholds', 'add them to the rule's frontmatter') with comprehensive niche coverage, but the second-person phrasing 'Use when you need to' violates the third-person guideline, reducing the score by 1.	4 / 5
Completeness	Both what (find, validate, and add packages) and when ('Use when you need to...') are explicitly present, but the when-clause restates the what rather than providing distinct concrete trigger phrases, leaving it short of fully explicit triggers.	4 / 5
Trigger Term Quality	Includes natural terms users would say such as 'npm packages', 'well-maintained', and 'frontmatter', but misses common synonyms and variations like 'dependencies', 'libraries', or 'install'.	4 / 5
Distinctiveness Conflict Risk	The narrow niche ('npm packages relevant to a frontend checklist rule', 'the rule's frontmatter') clearly distinguishes it from generic skills, with only minor overlap risk from broad package-research requests firing on 'npm packages'.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: thedaviddias/Front-End-Checklist
Path: skills/find-npm-packages/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.