Slicknode
v1.0.0Slicknode integration. Manage data, records, and automate workflows. Use when the user wants to interact with Slicknode data.
⭐ 0· 46·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 skill's name and description match the instructions: it is an integration that uses Membrane to access Slicknode. Minor inconsistency: the registry lists no required binaries, but the SKILL.md instructs installing and using the 'membrane' CLI (so in practice the skill expects that binary to be available). This is plausible but should have been declared.
Instruction Scope
The SKILL.md stays on scope: it instructs installing and using Membrane CLI commands to list/connect/run actions and to proxy requests to the Slicknode API. It does not tell the agent to read unrelated local files or environment variables. Note: requests are proxied via Membrane (external third party), so data and requests go off‑agent to Membrane's service as designed.
Install Mechanism
There is no formal install spec in the registry, but the instructions require installing @membranehq/cli globally via npm (npx is also used). Installing a global npm package executes third‑party code on the host (moderate risk), which is expected for a CLI integration but worth auditing the package/source before installing.
Credentials
The skill declares no required environment variables or credentials. Authentication is handled via Membrane's login flow (browser-based), so the skill does not request unrelated secrets. Be aware the Membrane CLI will manage and persist tokens locally as part of normal auth.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request permanent platform privileges or attempt to modify other skills. Allowing autonomous invocation is the platform default; nothing here increases privilege beyond normal expectations.
Assessment
This skill is a documentation-driven integration that expects you to install the Membrane CLI (npm: @membranehq/cli) and authenticate via a browser. Before installing: verify the Membrane package and publisher (npm and GitHub repo), be comfortable that API calls and auth tokens are proxied/stored by Membrane (requests will leave your machine to Membrane's service), and know that installing a global npm package runs third‑party code on your system. If you need to limit risk, review the CLI source, run it in an isolated environment, or ask for a version-pinned install from a known release.Like a lobster shell, security has layers — review code before you run it.
latestvk973hhqex63cz5fjyjfkd47qsn84ekdd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.