Opslevel
v1.0.0OpsLevel integration. Manage data, records, and automate workflows. Use when the user wants to interact with OpsLevel data.
⭐ 0· 51·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 (OpsLevel integration) matches the instructions: all actions are mediated via the Membrane CLI to talk to OpsLevel. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, logging in, creating a connection, listing/running actions, and proxying requests to OpsLevel. Important: the skill explicitly routes requests through Membrane's proxy, which will transmit request data (and any API payloads) to Membrane's service — this is expected for this integration but is a privacy/third-party-transmission consideration the user should be aware of.
Install Mechanism
There is no embedded install spec in the skill bundle (instruction-only). The instructions ask users to install the Membrane CLI via 'npm install -g @membranehq/cli' (or npx). Global npm installs are a common but moderate-risk operation — they write to system-wide locations and replace or shadow binaries; using 'npx' or a local install reduces that risk.
Credentials
The skill declares no required environment variables or credentials. Authentication is delegated to Membrane (browser-based login). No unrelated secrets or system configs are requested.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide settings in the instructions, and is user-invocable. Autonomous invocation remains allowed (platform default) but is not combined with any additional privileged access.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to OpsLevel. Before installing or using it, consider the following: (1) Membrane acts as a third-party proxy — any request/payload sent via the proxy will transit Membrane's service, so review Membrane's privacy, security, and data-retention policies and ensure you trust that provider with the data you will send. (2) Prefer ephemeral or least-privilege connections when possible and avoid sending sensitive secrets in free-form proxy requests. (3) Installing the CLI globally (npm -g) can modify system binaries; use 'npx' or a local install if you prefer not to change global state. (4) Verify the npm package and GitHub repository (package name @membranehq/cli and the listed repo) before installation to ensure you install the intended software. (5) If you need higher assurance, test in an isolated environment or with a non-production OpsLevel account first.Like a lobster shell, security has layers — review code before you run it.
latestvk970yw9zqw97fsrag2h6djk0hs84ddpz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.