Ip2Location

v1.0.0

IP2Location integration. Manage data, records, and automate workflows. Use when the user wants to interact with IP2Location data.

0· 59·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description say it's an IP2Location integration and the SKILL.md only instructs use of the Membrane CLI and Membrane connections to interact with IP2Location — the requested capabilities line up with the stated purpose.
Instruction Scope
The runtime instructions are limited to installing/using the Membrane CLI, creating a Membrane connection, listing actions, running actions, and proxying requests to IP2Location via Membrane. The doc does not instruct reading unrelated files, harvesting environment variables, or sending data to unexpected endpoints.
Install Mechanism
This instruction-only skill asks the user to install @membranehq/cli via npm (-g). Installing a global npm package is a reasonable requirement for a CLI-based skill but carries the normal npm/global-install risks (supply-chain/trust of the package and required privileges). No arbitrary download URLs or archive extraction are used.
Credentials
The skill declares no required environment variables or credentials and explicitly delegates authentication to Membrane. That is proportionate for a connector-based integration; the trade-off is trusting Membrane to manage API keys server-side.
Persistence & Privilege
The skill is not always-enabled, is user-invocable, and does not request persistent system-wide changes or access to other skills' configs. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill is coherent: it expects you to install the Membrane CLI and create a Membrane connection to IP2Location rather than providing API keys locally. Before installing, verify you trust the @membranehq/cli package and the Membrane service (they will manage your IP2Location credentials server-side). Installing a global npm package requires elevated filesystem permissions — consider installing in a controlled environment or using npx for one-off tests. Finally, be aware the CLI will make network requests and can proxy arbitrary API calls through your Membrane connection, so review any commands you run and the permissions granted to the connection.

Like a lobster shell, security has layers — review code before you run it.

latestvk970fpvzp3s2ym34g00vcjnk1x8499e4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments