Ipbase
v1.0.2Ipbase integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ipbase data.
⭐ 0· 114·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims an Ipbase integration and all runtime instructions use the Membrane CLI to talk to Ipbase, which is consistent. One small inconsistency: the registry metadata lists no required binaries, but the SKILL.md requires installing and running the 'membrane' CLI (installed via npm), so node/npm are implicitly required but not declared.
Instruction Scope
SKILL.md confines itself to using Membrane to discover connectors, create connections, run actions, and proxy requests to Ipbase. It does not instruct reading local files, environment variables, or transmitting data to unexpected endpoints beyond the Membrane proxy/Ipbase.
Install Mechanism
This is an instruction-only skill (no install spec in the registry), but the README instructs install via `npm install -g @membranehq/cli`. Installing an npm package is a common, moderate-risk action; the package appears to be from a named organization and an official site is in the doc, but the skill's manifest could have declared this requirement explicitly.
Credentials
The skill declares no required environment variables or credentials. The SKILL.md correctly directs the user to authenticate via the Membrane login flow and explicitly advises not to ask users for API keys. The need for a Membrane account is appropriate for the described behavior.
Persistence & Privilege
The skill is not set to always:true and is user-invocable. It does not request persistent system-wide privileges or modify other skills' configurations. Normal autonomous invocation is allowed by platform defaults and is not combined with other red flags here.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to proxy requests to Ipbase. Before installing, be aware you'll need node/npm to install the CLI and a Membrane account to authenticate. Review the @membranehq/cli npm package (and the Membrane privacy/security docs) so you’re comfortable that Membrane will hold and manage the Ipbase credentials. If you prefer not to install global npm packages on your main environment, consider using a container or isolated environment. Otherwise there are no other obvious mismatches or hidden credential requests in the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97aecp3p47kk9fbyr2s833grs842vtx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.