Nets Group
v1.0.2Nets Group integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nets Group data.
⭐ 0· 53·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 and description align with the content: all instructions target interacting with Nets Group via the Membrane platform/CLI. No unrelated credentials, binaries, or capabilities are requested.
Instruction Scope
SKILL.md stays on‑task: it instructs installing and using the Membrane CLI to create connections, list/run actions, and proxy raw Nets API requests. Important: requests and credentials are proxied through Membrane (i.e., data and auth are handled server-side by Membrane), which is expected but means network traffic and credentials are routed to Membrane's service.
Install Mechanism
No install spec in the registry package itself, but the README instructs npm install -g @membranehq/cli and also references npx @membranehq/cli@latest. Installing/running a third‑party npm CLI is a standard approach but carries moderate supply‑chain risk (package authenticity, global install privileges, running latest via npx).
Credentials
The skill declares no required env vars or secrets and explicitly instructs not to ask the user for API keys (Membrane handles auth). Requested scope of environment/credentials is minimal and consistent with the stated purpose.
Persistence & Privilege
Skill is instruction‑only, has no always:true flag, does not request persistent agent privileges, nor does it modify other skills or system settings.
Scan Findings in Context
[no_code_files] expected: This is an instruction‑only skill (SKILL.md). The regex scanner had no code to analyze; that's expected but means runtime risk is concentrated in the third‑party CLI the instructions ask you to install.
Assessment
The skill appears consistent with a Nets Group integration that uses Membrane as a proxy. Before installing/using it, verify the Membrane CLI package and its publisher (@membranehq) (check the npm page and the GitHub repo linked), avoid blindly running unfamiliar global npm installs, prefer running via npx in a controlled environment if possible, and review Membrane's privacy/security documentation so you understand what request payloads and credentials will be handled server‑side. If you must test in production, consider using a limited/test Nets account or token and monitor the created connection IDs and activity.Like a lobster shell, security has layers — review code before you run it.
latestvk9711a5waxkxhx64c6tcmc4pk1842y5p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.