21Risk
v1.0.221RISK integration. Manage data, records, and automate workflows. Use when the user wants to interact with 21RISK data.
⭐ 0· 41·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: 21RISK integration. The SKILL.md exclusively documents using the Membrane CLI to connect to 21RISK, discover actions, run actions, and proxy API calls — all coherent with the stated purpose. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are narrowly scoped to installing/using the Membrane CLI, performing login flows, creating a connection to 21RISK, listing actions, running actions, and proxying requests. The skill does not instruct reading arbitrary files or exfiltrating environment variables; it explicitly advises not to request API keys from users.
Install Mechanism
There is no automated install spec in the package (instruction-only). The SKILL.md tells users to install @membranehq/cli via `npm install -g` (and suggests `npx` elsewhere). Global npm installs execute remote code from the npm registry and require elevated permissions — this is a normal but higher-trust step the user must accept.
Credentials
The skill requests no environment variables or credentials. It relies on Membrane to manage credentials server-side and uses browser-based login flows — this is proportionate to a SaaS connector integration.
Persistence & Privilege
The skill does not request always:true or any elevated platform privileges. It's user-invocable and does not attempt to modify other skill configurations or system-wide settings.
Assessment
This is an instruction-only integration that uses the Membrane CLI to access 21RISK. Before installing or running commands: (1) confirm you trust Membrane/getmembrane.com (they will mediate access to your 21RISK account); (2) prefer using `npx @membranehq/cli@latest` instead of a global `npm install -g` if you want to avoid system-wide installs; (3) expect a browser-based login and that Membrane will hold/refresh credentials on your behalf — review their access scope and privacy policy; (4) be aware that running `npm` installs executes code from the npm registry, so only install packages from publishers you trust. If you need further assurance, verify the upstream repository (https://github.com/membranedev/application-skills) and the @membranehq/cli npm package before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97075d6s4f2bafargx65wsyph8436xz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.