Cusdis
v1.0.2Cusdis integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cusdis data.
⭐ 0· 75·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 (Cusdis integration) line up with the SKILL.md, which instructs use of the Membrane CLI to manage Cusdis connections, actions, and proxy requests. No unrelated services or credentials are requested.
Instruction Scope
Instructions are focused on using the Membrane CLI (login, connect, action list/run, request proxy). They do allow sending arbitrary proxied API requests via Membrane, so users should understand that API calls and payloads will transit Membrane's service. The instructions do not direct reading of local files or unrelated env vars.
Install Mechanism
The skill is instruction-only (no install spec). It tells users to install @membranehq/cli via npm -g or use npx; using npm -g modifies the system environment and requires package manager access. This is expected for a CLI-based integration but is a system-level action the user must consent to.
Credentials
No environment variables or secrets are requested by the skill. Authentication is delegated to Membrane (browser login flow). This is proportional for a proxy/connector-based integration, but note that Membrane will handle and see auth tokens and proxied requests to Cusdis.
Persistence & Privilege
The skill is not always-enabled and doesn't request elevated persistent privileges. It does rely on the user installing a CLI tool if they want to run commands, but the skill itself does not modify other skill configs or require permanent system presence.
Assessment
This skill is coherent for managing Cusdis via Membrane, but before installing or using it: (1) Confirm you trust Membrane (their service will see proxied requests and hold connection credentials). Review Membrane's privacy and access controls and the connector permissions. (2) Prefer using npx for one-off commands if you don't want a global npm install; global install alters your system PATH and requires appropriate privileges. (3) Be aware the agent can run networked Membrane commands — only allow autonomous use if you trust it to make API calls on your behalf. (4) Verify connector IDs and review actions returned by membrane action list to avoid inadvertently sending sensitive payloads through the proxy.Like a lobster shell, security has layers — review code before you run it.
latestvk97fk8aedq6715erke73vd7g2184348n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.