Aruba Networks

v1.0.0

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

0· 63·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
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the instructions: the skill is an Aruba Networks integration and all runtime guidance is about using the Membrane CLI to connect to Aruba. No unrelated credentials, binaries, or system paths are requested.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying API requests. It does not instruct reading arbitrary files or env vars on the host. It does route requests and authentication through Membrane (so Membrane will see proxied requests and credentials).
Install Mechanism
There is no registry install spec; the skill is instruction-only and asks the user to run `npm install -g @membranehq/cli` (or use npx). Installing a CLI from npm is a reasonable requirement but does carry the usual trust/import risk of global npm packages—the guidance to prefer Membrane is appropriate.
Credentials
The skill declares no required environment variables or secrets. Authentication is delegated to Membrane (browser-based login/connection creation), so no local API keys are requested. Because Membrane manages credentials server-side, users should understand Membrane will hold and use those credentials.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system changes or elevated privileges. It is instruction-only and does not modify other skills or system-wide settings.
Assessment
This skill is instruction-only and appears coherent: it tells you to use the Membrane CLI to connect to Aruba Networks and to let Membrane manage auth. Before installing or using it, verify you trust the Membrane service and the @membranehq/cli npm package (review the homepage and the referenced GitHub repository), prefer using `npx` if you want to avoid a global npm install, and be aware that proxied requests and credentials will be handled server-side by Membrane (so Aruba data will transit their service). If you need stricter control over credentials or data residency, investigate Membrane's privacy/security documentation or use Aruba's direct API with your own credential management.

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

latestvk978b46892x30nd2zfbm1vdpnh845rdy

License

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

Comments