Hotspotsystem
v1.0.2HotspotSystem integration. Manage Organizations, Users, Projects. Use when the user wants to interact with HotspotSystem data.
⭐ 0· 122·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 name/description describe a HotspotSystem integration and all runtime instructions are about using the Membrane CLI to connect to HotspotSystem, list actions, run actions, or proxy API requests — which fits the stated purpose.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating connections, listing/running actions, and proxying requests. It requires network access and a Membrane account (documented). It does not ask the agent to read unrelated local files or other credentials.
Install Mechanism
There is no install spec in the skill bundle (instruction-only), but the instructions tell the user to run `npm install -g @membranehq/cli`. That is a reasonable, common way to obtain a CLI; note the usual supply-chain considerations when installing global npm packages (verify package identity, prefer official sources).
Credentials
The skill does not declare or require any environment variables or credentials beyond having a Membrane account. The runtime flow uses the Membrane CLI's interactive/browser auth — this is proportionate to the integration's needs.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It is an instruction-only skill that relies on the user/agent invoking CLI commands; autonomous invocation is allowed by default but is not combined with broad credential requests or persistent, unexplained access.
Assessment
This skill is coherent: it instructs the user/agent to install and use the official Membrane CLI to talk to HotspotSystem. Before installing or running commands, verify the npm package (@membranehq/cli) is the legitimate source (check its npm/GitHub pages and maintainers). Installing a global npm package requires appropriate local privileges — avoid installing on sensitive/production hosts unless you trust the package. Be aware the Membrane CLI will handle and store authentication tokens locally after login; if you later wish to revoke access, use Membrane’s account or CLI logout/revoke features. If you need stricter controls, test the workflow in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk977skd706gea9k1qeynr4xmbs842vw5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.