name-check

Solid

Suggests project/crate/plugin names and checks availability across registries (crates.io, npm, PyPI, AUR, GitHub, domains; needs `bun`). Use before naming, renaming, or publishing anything.

AI & Automation 5 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
26
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Name Check ## Procedure 1. **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) 2. **Generate 10-30 candidates.** Brainstorm and balance three axes: - explicit: name states the function (`kate-markdown-preview` over `katdown`) - 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`). 3. **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) 4. **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 sp...

Details

Author
uwuclxdy
Repository
uwuclxdy/agenticat
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

domain-check

Reconcile domain-name availability across sources that disagree. Registrar availability endpoints report registered, broker-parked domains as available; this skill fixes the precedence — RDAP (Registration Data Access Protocol) is authoritative, DNS (Domain Name System) corroborates, broker nameservers override any "available", and the registrar is consulted for price only. Works on one domain or a bulk candidate sweep. Trigger via /domain-check, "is this domain available", "check these domain names", "did the availability tool lie". Not /investigate (read-only fact-gathering over a codebase) or /double-check (re-verifies one already-stated claim) — domain-check owns the availability verdict itself.

0 Updated today
allemaar
AI & Automation Listed

bs-check

Use before telling a client or stakeholder "this is fixed", before deploying changes to a production site or service, before activating or modifying a live automation/workflow, before claiming an integration works end-to-end, before quoting pricing or API behavior in a comparison, or before running a destructive infrastructure command. Also use when the user says "confidence check", "how confident are you", "validate this", "pressure-test this", "/bs-check", or whenever a confident-sounding claim has not been directly validated by a query, observation, comparison, or quotable source. ALSO covers design-time reasoning audits via subcommands - "bs-check premise" (are we solving the right problem? premise acceptance - Socratic + Steelman), "bs-check approach" (did we commit too fast? - Burden of Proof, Cold Start, Alternatives, Pre-mortem), "bs-check fresh" (all 9 patterns, fresh-context sub-agent). Trigger phrases for those - challenge this, push back, devil's advocate, poke holes, steelman this, are we solving

0 Updated today
GemSpecter
AI & Automation Listed

business-name-fit

Help a founder pick or vet a business, startup, or product name that stays true to their cultural origin while working well in the markets they want to sell into. Use whenever someone is naming a company, brand, or product and cares about how it lands across languages and regions — for example a name that sounds right at home but might read oddly to English speakers, or an authentic name they want to check before committing. Trigger this for any request about choosing a business name, checking if a name "works" abroad, spotting bad meanings in other languages, or making a name sound trustworthy in a specific market — even if the person doesn't say the word "skill".

2 Updated yesterday
elfarajnejad-commits