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.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Identify, validate, and add npm package references to a Front-End Checklist rule.
Given a rule file or rule slug, this skill will:
npmPackages frontmatter fieldBefore selecting any package, check it against these criteria using the npm registry:
| Criterion | Minimum |
|---|---|
| Weekly downloads | >10,000/week |
| Last publish | Within 18 months |
| npm registry | Must be listed (registry.npmjs.org/{name}) |
Packages that fail any threshold must be excluded, regardless of how relevant they are.
Read the rule file: packages/content/rules/en/{category}/{slug}.mdx
Focus on:
tools: field?Search for packages that:
Use https://www.npmjs.com/search?q={keywords} and knowledge of the ecosystem to find candidates.
Prefer packages that are:
eslint, stylelint, official plugins)For each candidate package, fetch and verify:
# Metadata
curl https://registry.npmjs.org/{package}/latest | jq '{name, version, description}'
# Weekly downloads
curl https://api.npmjs.org/downloads/point/last-week/{package} | jq '.downloads'Record the weekly download count and last publish date. Reject any below threshold.
Add a npmPackages array to the frontmatter with the package names only (metadata is fetched at build time):
npmPackages:
- eslint
- eslint-plugin-jsx-a11y
- axe-corePlace it after tools: and before resources:.
Run the validation script to confirm all packages pass thresholds:
pnpm validate:packages packages/content/rules/en/{category}/{slug}.mdxIf any package fails, either remove it or replace it with a better alternative.
For the rule accessibility/form-labels:
npmPackages:
- eslint-plugin-jsx-a11y
- axe-core
- @testing-library/jest-domAll three have >100k weekly downloads and were published within the last 6 months.
thedaviddias/Front-End-Checklist
e8d14d0
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.