Softlayer
v1.0.2SoftLayer integration. Manage data, records, and automate workflows. Use when the user wants to interact with SoftLayer data.
⭐ 0· 93·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
The name/description match the instructions: the SKILL.md guides the agent to use the Membrane CLI to access SoftLayer. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions focus on installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to SoftLayer via Membrane. They do not instruct reading unrelated files or environment variables, nor transmitting data to unexpected endpoints beyond Membrane/SoftLayer.
Install Mechanism
The skill recommends installing the @membranehq/cli globally via npm (npm install -g). This is a common install route but carries the usual supply-chain/trust considerations for npm packages; the skill itself has no install spec and writes nothing to disk automatically.
Credentials
No environment variables or credentials are requested by the skill. The README explicitly directs using Membrane-managed connections instead of asking for API keys locally, which is proportionate to the described behavior.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system privileges. It relies on an external CLI and browser-based login; autonomous invocation is allowed by default (platform norm) but not combined with other concerning privileges.
Assessment
This skill is an instruction-only integration that delegates SoftLayer access to the Membrane CLI/service. Before installing or using it: 1) Verify you trust Membrane (@membranehq) — review the npm package, its publisher, and the linked GitHub repo; 2) Understand that authentication happens via browser/your Membrane account and that API calls will be proxied through Membrane (so review their privacy/access policies for your data); 3) Installing the CLI globally with npm is convenient but carries standard supply-chain risks—prefer auditing the package version or using npx in sensitive environments; 4) If you manage sensitive infrastructure, confirm that Membrane's access model and scope of the connection are acceptable before creating connections to production SoftLayer accounts.Like a lobster shell, security has layers — review code before you run it.
latestvk97542fqvz3jw11j28spk1mm5x843k3x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.