Name check
Suggests project/crate/plugin names and checks availability across registries (crates.io, npm, PyPI, AUR, GitHub, domains). Use before naming, renaming, or publishing anything.From its SKILL.md
npx -y skills add uwuclxdy/agenticat --skill name-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.1 KB, as published. Nobody here has run it
Name Check
Procedure
- Scope first (before a rename or release). Establish from context (ask if unsure):
- what the thing does, in one line
- which registries matter: crates.io, AUR, PyPI, npm, GitHub, KDE store, domain... Check only relevant registries depending on the project.
- rename cost: unpublished (cheap, anything goes) vs already public (flag every rename consequence)
- Generate 10-30 candidates. Brainstorm and balance three axes:
- explicit: name states the function (
kate-markdown-previewoverkatdown) - brandable: short, lowercase, occasionally punny (
flit,nook,perch) - user-fit: closest to the user's stated direction Mark each candidate with which axis it leans toward. Reserve companion names too when relevant (
flit+flitd+flit-mcp).
- explicit: name states the function (
- Check availability in parallel. Fan out searches (web + registry pages) per candidate:
- exact match on each relevant registry
- general web collision: existing project, product, or company with the same name in the same space
- near-collisions worth flagging (one-letter-off popular project, trademark-adjacent)
- Report as a table with these columns:
| candidate | <one column per relevant registry> | web collision | note |
|---|
free / taken (link) / near: <what> per cell. End with one recommendation and why.
Helper
name-check.ts (same dir as the skill, requires bun) runs the deterministic registry axis in one pass to spare you the manual fetching:
bun name-check.ts <name> [<name>...] [--table] [--registry npm,crates,...] [--tld com,io]
- compact JSON by default;
--tablefor a quick scan,--listfor registry ids. - supports npm, PyPI, crates.io, RubyGems, Hackage, Go, Docker (library), Homebrew, AUR, NuGet, GitHub, plus domain availability (RDAP, DNS-confirmed on a 404).
- domain checks run only when
--registryis unset or explicitly includesdomain(e.g.--registry npm,domain). The flag is not additive by default for domains. - does not do web collision. still run that axis via WebSearch (same-space products, companies, trademarks) and fold both into the report table. Not a legal trademark search either (see Rules).
- registry read-only.
Rules
- Never reserve, publish, or rename anything. This flow is report only; renames require user's call.
- "Free" claims must come from an actual lookup this session, not memory.
- If every candidate is taken, say so and generate a second batch instead of stretching a bad fit. Taken by an abandoned or dead project still counts as taken. Do not attempt reclaim, transfer, or dispute (each registry has its own policy for that). Report it as taken and let the user decide.
- Registry and WebSearch checks are not a legal trademark search. Flag trademark-adjacent hits. Tell the user to run a formal search (USPTO, EUIPO, local registry) before any commercial release.
What ships with it: 1 file
15.2 KB alongside SKILL.md, 1 of them executable
- name-check.tsruns15.2 KB
Gives 0 of the 12 instructions most quality gates skills give
Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06
- Read full output and check exit codein 45 of 1524, across 40 files
- Verify output confirms the claimin 44 of 1524, across 39 files
- Identify the command that proves the claimin 43 of 1524, across 39 files
- Execute the full verification commandin 36 of 1524, across 30 files
- Produce a verification reportin 34 of 1524, across 18 files
- Review git diff changesin 30 of 1524, across 16 files
- Fix build failures immediatelyin 29 of 1524, across 9 files
- Group findings by severityin 28 of 1524
- State claim only with evidencein 27 of 1524, across 22 files
- Verify regression tests with red-green cyclein 26 of 1524, across 22 files
- Run the full test suitein 26 of 1524, across 25 files
- Run test suite with coveragein 25 of 1524, across 10 files
Said here and by no other author read
- Identify project function and relevant registries
- Generate ten to thirty name candidates
- Categorize candidates by explicit, brandable, or user-fit axes
- Check availability across all relevant registries
- Perform web search for name collisions
- Flag trademark-adjacent names
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.