Unzer
v1.0.0Unzer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Unzer data.
⭐ 0· 70·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/description (Unzer integration) matches the instructions: it uses Membrane CLI to create connections, list actions, run actions, and proxy requests to the Unzer API. Nothing requested or described appears unrelated to interacting with Unzer via Membrane.
Instruction Scope
SKILL.md confines runtime behavior to installing/using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests to Unzer. It does not instruct reading arbitrary files, exfiltrating environment variables, or modifying unrelated system configuration.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells users to install a public npm package (@membranehq/cli) globally or use npx. Using npm is a common, reasonable choice, but it does mean arbitrary code from the npm registry will run on the machine. The skill metadata did not declare a required CLI binary even though the instructions require membrane on PATH — minor mismatch.
Credentials
The skill declares no required environment variables or credentials and explicitly advises against asking users for API keys (Membrane handles auth). The auth flow is delegated to Membrane (browser OAuth), which is coherent with the skill's purpose.
Persistence & Privilege
The skill does not request always:true and does not claim to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) and is appropriate for an integration skill.
Assessment
This skill is coherent but depends on the Membrane service and its CLI. Before installing or using it: 1) Verify the npm package @membranehq/cli and its publisher on the npm registry and inspect the package (or prefer using npx to avoid a global install). 2) Confirm you trust Membrane/getmembrane.com because the CLI will open a browser-based login and Membrane will proxy requests to Unzer (so Membrane will be able to access your Unzer data). 3) Note the SKILL.md expects the membrane CLI on PATH even though the registry metadata didn’t list it as a required binary — ensure you have Node/npm and are comfortable installing third-party CLI tools. 4) If you need stricter control, consider creating a limited test account in Unzer and Membrane first.Like a lobster shell, security has layers — review code before you run it.
latestvk9706e0pd9fab8c5p2yg5a02yd844tj8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.