AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Name Check

skill-uwuclxdy-agenticat-name-check · by uwuclxdy

Suggest project/crate/plugin names and verify availability across registries (crates.io, npm, PyPI, AUR, GitHub, domains). Use before naming, renaming, or publishing anything.

↗ Repository
— No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-uwuclxdy-agenticat-name-check

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-uwuclxdy-agenticat-name-check)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Name Check? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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)
  1. 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).

  1. 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)
  1. Report as a table with these columns:

| candidate | | web collision | note | |---|---|---|---|

free / taken (link) / near: 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 [...] [--table] [--registry npm,crates,...] [--tld com,io]

  • compact JSON by default; --table for a quick scan, --list for 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).
  • does not do web collision. still run that axis via WebSearch (same-space products, companies, trademarks) and fold both into the report table.
  • 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools