This skill should be used when the user wants to find an available npm package name, check whether one or more names are taken on the npm registry, brainstorm name ideas for a package, or pre-flight a name against the moniker (similar-name) collision rule before publishing. Common triggers include "find me an npm name for", "is <name> available on npm", "check if these package names are taken", "brainstorm a name for my package", "help me name this npm package", and "will <name> hit moniker coll
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/4/2026
What it changes
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
Without skill32%
With skill73%
Checks it passed that the model alone missed
The CLI command includes --limit 200 when invoking check.mjs.
The CLI command includes --scope @acme when calling check.mjs.
The CLI command includes --near-distance 3 when running check.mjs.
and 9 more in the full report
12 fixed4 passed either way3 still failing3 broke
Pass-rate lift
+41 pp
Tokens
+139%
Agent turns
0%
Response time
-58%
Model gemini-3.6-flashMeasured 8/4/2026v116 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
I want to search for available package names under my npm org scope @acme using the seed terms build and bundle. What option specifies the scope when executing candidate check scripts?
What was checked, without and with the skill
Checked
Without skill
With skill
The CLI command includes --scope @acme when calling check.mjs.
Missed
Passed
case-04 · gemini-3.6-flash · 8/4/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md188 lines2 files
npm-namer
Finds available npm package names. Bundles a Node script (scripts/npm-namer/dist/check.mjs) that runs four layers of check:
Syntactic validation — thin wrapper over the official validate-npm-package-name package (uppercase, leading char, length, URL-safe, core-module shadow, etc.)
Availability — parallel HEAD requests to registry.npmjs.org for each candidate
Near-match (typosquat) warning — Damerau-Levenshtein distance against the top ~15,000 most-downloaded npm packages (TypoGard's published threshold, sourced from nice-registry/download-counts); catches extoolkit as suspiciously close to es-toolkit even though it would publish fine per the moniker rule
The full rule set the script encodes is in references/moniker-rules.md — load that when the user asks why a name fails.
Inputs
$ARGUMENTS — one of:
Seeds + concept: "i want a tiny logging lib. seeds: tinylog, microlog, jslog" → permute + check
Concept only: "name a cli that queries bigquery in the terminal" → brainstorm seeds, then permute + check
Pre-checked list: "are these taken? a, b, c, d" → batch check only, no brainstorming
Empty → ask what kind of package needs naming
Workflow
1. Classify the request
Signal in the prompt
Mode
User gave explicit seed words or candidates
find (permute the given seeds)
User described a concept but listed no names
brainstorm-then-find (you generate seeds, then permute)
User listed names asking "which are taken?"
check (batch check only, skip permutation)
If unclear, ask once with concrete options. Default to brainstorm-then-find when the user describes a package concept.
2. Brainstorm seeds (only in brainstorm-then-find mode)
Generate 10–20 candidate seed words that capture the concept's essence. Mix:
Direct nouns from the concept ("log", "bigquery", "query")
Metaphors ("forge", "sage", "smith", "lens")
Compact forms ("bq", "sql", "log")
Verbs that describe what the tool does ("scout", "probe", "ping")
This skill should be used when the user wants to review, audit, or sanity-check an existing agent skill in this repo against authoring conventions. Common triggers include "review the X skill", "audit this skill", "check skill X against repo conventions", "is this skill any good", "second opinion on skill X", "sanity check skill X", and "review skill X before publishing". Produces a severity-tiered report (error / warn / info) with a Clean section even on pass, and classifies the skill type. Ski