Whois Checker
v4.0.1Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Whois Checker concepts, best practices, and implementation patterns.
⭐ 0· 363·1 current·1 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Whois Checker reference tool) match the provided assets: an instruction-only SKILL.md and a local shell script that prints reference documentation. There are no unexpected env vars, binaries, or external services required.
Instruction Scope
SKILL.md explicitly states all output is plain-text via heredoc and no external API calls or network access are needed. The included scripts/script.sh only prints embedded documentation and does not read files, environment variables, or make network calls.
Install Mechanism
No install spec is present (instruction-only with an auxiliary script). No downloads, package installs, or extract operations are specified — the script is shipped in the bundle and nothing is written to disk beyond what the platform already does when installing the skill.
Credentials
No environment variables, credentials, or config paths are required. The skill does not access or declare secrets; the requested privilege surface is minimal and proportional to a local reference tool.
Persistence & Privilege
always is false and the skill does not request persistent or elevated privileges. It does not modify other skills or system-wide configuration and contains no install-time hooks.
Assessment
This skill appears to be a simple local reference tool and is internally consistent. If you plan to install it: (1) review the scripts/script.sh contents (already benign: only prints docs) and run it in a sandbox or container if you want to be extra cautious; (2) note a minor non-security inconsistency — the script's VERSION is 4.0.0 while registry lists 4.0.1 — which looks like a packaging/versioning bug rather than malicious behavior; (3) avoid granting any additional credentials or environment variables to this skill unless future versions explicitly require them and you understand why. If you need higher assurance, ask the maintainer for a signed release or run the code in an isolated environment before trusting it in production.Like a lobster shell, security has layers — review code before you run it.
latestvk970a9g5x4njphrwgn805wgz7d83gsb9productivityvk970zxbkqqewseezeeqd9fn52x82rj0e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.