Scalr
v1.0.2Scalr integration. Manage Organizations, Users, Goals. Use when the user wants to interact with Scalr data.
⭐ 0· 113·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 match the runtime instructions: the SKILL.md instructs using the Membrane CLI to connect to Scalr, list actions, run actions, and proxy API calls. All required operations are coherent with managing Scalr objects (Organizations, Users, Goals).
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, performing login flows, creating connections, discovering and running actions, and proxying Scalr API endpoints via Membrane. The instructions do not ask the agent to read unrelated files or environment variables. They do permit proxying arbitrary Scalr API paths (expected for an integration).
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to install @membranehq/cli via 'npm install -g'. Installing from the public npm registry is a reasonable, common choice, but global npm installs modify the host environment—users should confirm the package identity (publisher, homepage) before installing. The README also suggests npx in places (less persistent).
Credentials
The skill requests no environment variables or credentials. It explicitly delegates auth to Membrane's browser-based login/connection flow so local secrets aren't requested. This is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request always: true, does not modify other skills or global agent config in the instructions, and requires only normal network access and the Membrane CLI. Autonomous invocation is enabled by default but is not combined with other concerning privileges here.
Assessment
This skill delegates Scalr API access through Membrane. Before installing or using it: (1) Verify you trust Membrane (getmembrane.com, @membranehq on npm, and the GitHub repository) because API traffic and auth flows go through their service; (2) Prefer using npx or a local install if you want to avoid a global 'npm -g' install; (3) Review the Membrane CLI package on npm/github to ensure it's the official publisher and the version you install is expected; (4) Use least-privilege Scalr accounts when connecting (avoid giving a connector broad admin access unless required); (5) Be aware that proxying arbitrary API paths will expose the data in those calls to Membrane's service—do not send sensitive data you wouldn't want routed through a third party.Like a lobster shell, security has layers — review code before you run it.
latestvk97d4qkycyvrqvt7bpmv0gwa45843am7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.