Ip2Whois
v1.0.0IP2WHOIS integration. Manage data, records, and automate workflows. Use when the user wants to interact with IP2WHOIS data.
⭐ 0· 56·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description state an IP2WHOIS integration and the SKILL.md exclusively documents using the Membrane CLI to discover connectors, create a connection, run actions, and proxy API calls. Requests for network access and a Membrane account are proportional and expected.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, logging in, discovering connectors/actions, running actions, and proxying requests to the IP2WHOIS API. The SKILL.md does not instruct reading unrelated local files, inspecting environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
No built-in install spec (skill is instruction-only). The doc recommends installing @membranehq/cli via npm (global install). This is a common, reasonable approach for a CLI integration but carries the usual supply-chain considerations of installing third-party npm packages globally.
Credentials
The skill declares no required env vars, credentials, or config paths. It instructs using Membrane's managed connections (so credentials are handled server-side) which aligns with the stated goal; there are no disproportionate secret requests.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent or privileged system presence, nor does it instruct modifying other skills or system-wide agent settings.
Assessment
This skill is instruction-only and coherent: it tells you to install the official Membrane CLI and use it to manage an IP2WHOIS connector. Before installing/running the CLI: (1) verify the @membranehq/cli package on npm (publisher, downloads, source) and prefer installing in a controlled environment (container/VM) rather than globally on a production host; (2) understand that using Membrane delegates credential handling to their service — you are trusting Membrane with the connector authentication; (3) be cautious when using the proxy feature (membrane request) — avoid sending unrelated sensitive files or secrets in proxied requests; (4) if you need higher assurance, review the Membrane CLI source (GitHub link in SKILL.md) and the service's privacy/auth policies before supplying credentials via the login flow.Like a lobster shell, security has layers — review code before you run it.
latestvk971hfstzr3zfcd0djrjytgdt584cw1g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.