Switchboard

v1.0.2

Switchboard integration. Manage Organizations, Users. Use when the user wants to interact with Switchboard data.

0· 107·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The README describes integrating with Switchboard via the Membrane CLI. The commands and flows in SKILL.md (login, connect, action list/run, request proxying) match that purpose and require a Membrane account and network access — which are reasonable and expected.
Instruction Scope
The runtime instructions focus on installing and using the Membrane CLI and on creating/using Switchboard connections. They do not instruct reading unrelated local files, accessing unrelated environment variables, or exfiltrating data. Proxy functionality is explicit (membrane request) and documented; the skill instructs browser-based auth for the user.
Install Mechanism
This is an instruction-only skill (no install spec), but SKILL.md tells users to install @membranehq/cli from npm (global install or npx). Installing an npm CLI is a common and expected step for this integration, but npm packages run code during install — so installing CLI software from the public registry has moderate supply-chain risk and should be verified (publisher, package integrity).
Credentials
The skill does not request environment variables or credentials in its manifest and explicitly advises against asking users for API keys (use Membrane connections). Requiring a Membrane account and browser-based login is proportionate to the stated functionality.
Persistence & Privilege
The skill is not always-enabled and contains no install-time code or files that would persist on the agent. It does not request elevated or cross-skill configuration changes.
Assessment
This skill is coherent for interacting with Switchboard through Membrane, but take standard precautions before installing a third-party CLI: verify the npm package author (@membranehq) and package version, prefer running via npx or installing in an isolated environment/container rather than a global install, inspect the package files if possible, and be aware that Membrane acts as a proxy and will see/request access to the target Switchboard account data (so review Membrane's privacy/security docs). If you cannot verify the CLI publisher or want lower risk, avoid global installs and run commands in a sandbox or ask for more provenance (e.g., link to the exact npm package/release).

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

latestvk970y4axq7tcfejj3fsdepm6eh843bh6

License

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

Comments