Wp Maps
v1.0.2WP Maps integration. Manage data, records, and automate workflows. Use when the user wants to interact with WP Maps data.
⭐ 0· 72·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
Name/description (WP Maps integration) match the instructions: the SKILL.md documents using Membrane to connect to WP Maps and run actions or proxied API requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions only guide installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to the WP Maps API. They do not ask the agent to read unrelated files, request unrelated environment variables, or send data to unexpected endpoints beyond Membrane/WP Maps.
Install Mechanism
There is no automated install spec in the skill bundle (lowest-risk). The doc recommends installing @membranehq/cli via npm -g, which is a common but system-level operation — expected for this integration but worth noting before you run global npm installs.
Credentials
The skill requests no local env vars and defers credential handling to Membrane. This is proportionate to the stated purpose, but it does imply trusting Membrane with proxied requests and authentication tokens (data/requests will flow through Membrane's service).
Persistence & Privilege
The skill is not marked always:true and has no install artifacts. It is user-invocable and can be called autonomously by the agent by default (platform default) — this is normal and not by itself a concern.
Assessment
This skill is an instruction-only integration that expects you to use the Membrane CLI to manage WP Maps; it does not request local secrets. Before installing or using it: (1) confirm you trust Membrane (getmembrane.com/@membranehq/cli) because traffic and credentials will be proxied through their service; (2) be aware the documentation asks you to run a global npm install (npm install -g), which requires appropriate system privileges — consider installing in a controlled environment or using npx/local install if preferred; (3) if you want to limit automation, review or disable autonomous invocation for this skill in your agent settings before granting it run privileges; (4) if you need stronger data privacy, consider integrating directly with your WP Maps instance/API rather than proxying through a third-party service.Like a lobster shell, security has layers — review code before you run it.
latestvk97d5xk309xpqz4s87dd7gjhdn8433yc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.