Scaled Access
v1.0.2Scaled Access integration. Manage data, records, and automate workflows. Use when the user wants to interact with Scaled Access 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
medium confidencePurpose & Capability
Name/description match the instructions: it uses the Membrane CLI to connect to Scaled Access, list actions, run actions, and proxy API requests. Required capabilities (network access, Membrane CLI) are what you'd expect for this integration.
Instruction Scope
SKILL.md instructs the agent/user to install and use Membrane CLI, create connections via browser-based auth, list and run actions, and use Membrane's proxy to call Scaled Access APIs. These steps are within the integration scope, but they imply that requests and data will flow through Membrane's servers (the skill does not explicitly detail what data is transmitted or logged).
Install Mechanism
No install spec in the registry; the SKILL.md recommends installing @membranehq/cli via npm (-g) or using npx. Installing a global npm package is a common pattern but has moderate risk compared to instruction-only skills (packages execute code on your machine). This is expected for a CLI-based integration.
Credentials
The skill does not request environment variables, secrets, or config paths. It relies on Membrane to manage credentials, which is proportionate to the stated approach, though this centralization means credentials and proxied requests are handled by Membrane (third-party).
Persistence & Privilege
Skill is instruction-only, not always-enabled, and user-invocable. It does not request permanent agent privileges or modify other skills; autonomous invocation is allowed (platform default) but not elevated here.
Assessment
This skill appears to do what it says: it uses Membrane's CLI to integrate with Scaled Access. Before installing, verify you trust Membrane (https://getmembrane.com and the referenced repo), because authentication and proxied API requests travel through their service. Consider: 1) prefer npx or local install instead of npm -g if you don't want a global package; 2) review Membrane's privacy/security docs and the CLI package source (GitHub) to confirm handling of credentials and logs; 3) test in a non-production account first; and 4) don't enter unrelated credentials or secrets—Membrane should manage only the connector auth as described. If you need higher assurance, ask for the exact repository commit or a signed release for the @membranehq/cli package.Like a lobster shell, security has layers — review code before you run it.
latestvk970myfjfv0g7nbqkta1d7c8m18432bv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.