Scopemaster
v1.0.2ScopeMaster integration. Manage Organizations, Users. Use when the user wants to interact with ScopeMaster data.
⭐ 0· 88·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (ScopeMaster integration) match the instructions: the SKILL.md describes using the Membrane CLI to discover and run ScopeMaster-related actions and proxy API calls. Nothing requested (no env vars, no config paths) is inconsistent with that purpose.
Instruction Scope
Runtime instructions are focused on installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to ScopeMaster via Membrane. The doc does not instruct reading local files or unrelated environment variables, nor does it direct data to unexpected external endpoints beyond Membrane/ScopeMaster.
Install Mechanism
There is no formal install spec in the registry metadata (skill is instruction-only), but the SKILL.md tells users to install @membranehq/cli via npm (npm install -g). Installing a global npm package is a typical but non-trivial operation — the package comes from the public npm registry (not an arbitrary URL).
Credentials
The skill declares no required environment variables or credentials and explicitly instructs using Membrane-managed connections rather than asking for API keys locally. Requested privileges are proportionate to the stated integration purpose.
Persistence & Privilege
The skill is not marked always:true and does not request persistent system-level changes. It is an instruction-only skill that relies on the user installing a CLI; it does not modify other skills or ask for system-wide config paths.
Assessment
This skill appears to do what it says: it relies on the official Membrane CLI to connect to ScopeMaster and does not request unrelated secrets. Before installing: verify the @membranehq/cli package and its publisher on npm (or install in an isolated environment), confirm the getmembrane.com project is the intended provider, and be aware that using the CLI grants network access to Membrane and (via it) to ScopeMaster — ensure you trust those services and the connection IDs you create. If you need stricter controls, run the CLI in a sandbox or container and review the npm package source/repo first.Like a lobster shell, security has layers — review code before you run it.
latestvk97bd4wr4k0cmmv8cjz24fh1z5842qtv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.