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

76%

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

77%

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

A highly actionable, well-sequenced workflow with strong validation feedback loops, slightly weakened by redundancy between sections and the absence of any progressive disclosure into bundle files. The procedural guidance itself is concrete and complete.

Suggestions

Remove the "What NOT to do" section or fold its unique points ("no versions", "no tangentially-related packages") into the thresholds table, since the <10k downloads and >18-month rules already appear there — this cuts redundant tokens.

Move the worked "Example output" and detailed validation-script behavior into a short reference file (e.g. references/validation.md) and link to it one level deep, improving progressive disclosure without bloating SKILL.md.

Merge "What this skill does" with "Research steps" so the five-step list is the single source of truth for the process.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not over-explain concepts Claude knows, but the "What NOT to do" list restates the mandatory thresholds table and "What this skill does" overlaps the numbered research steps, so it could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready executable commands (curl/jq for npm registry and downloads, pnpm validate:packages) and exact rule file paths, leaving no step abstract.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with an explicit validation checkpoint ("Validation after adding") and a fix/remove/retry feedback loop for the batch package operation, satisfying the rubric's feedback-loop requirement.	3 / 3
Progressive Disclosure	Well-organized into clear sections but presented as a single monolithic ~120-line file with no bundle references; the validation details and worked example are inline rather than split out one level deep.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 specific, well-scoped description with an explicit trigger and low conflict risk, held back only by second-person voice and limited trigger-term variation. It clearly states both the task and the activation condition.

Suggestions

Rewrite in third person to avoid the specificity penalty: e.g., "Finds, validates, and adds the 2-3 most popular well-maintained npm packages to a frontend checklist rule's frontmatter. Use when adding npm packages or dependencies to a rule."

Broaden trigger terms to include natural phrasings like "dependencies", "libraries", or "adding packages to a checklist rule" so users are more likely to phrase the request matching this skill.

Dimension	Reasoning	Score
Specificity	Names 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") which would score 3, but the second-person voice ("Use when you need to find") triggers the rubric's -1 specificity penalty.	2 / 3
Completeness	Explicitly answers both what (find, validate, add packages to frontmatter) and when via the "Use when you need to find... relevant to a frontend checklist rule" trigger clause.	3 / 3
Trigger Term Quality	Includes the natural term "npm packages" plus "frontend checklist rule" and "frontmatter", but omits common variations a user might actually say such as "dependencies", "libraries", or "adding packages to a rule".	2 / 3
Distinctiveness Conflict Risk	A clear niche — npm packages for frontend checklist rule frontmatter — with distinct triggers, making overlap with unrelated skills unlikely.	3 / 3
	Total	10 / 12 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: 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.