Automizy
v1.0.2Automizy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Automizy data.
⭐ 0· 129·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 and description match the instructions: all runtime steps are about using the Membrane CLI to connect to Automizy, list actions, run actions, or proxy API requests. No unrelated credentials, binaries, or system paths are requested.
Instruction Scope
Instructions are narrowly scoped to installing and using @membranehq/cli (login, connect, action run, request proxy). They do not direct the agent to read arbitrary files or harvest unrelated environment variables. Note: proxying requests via Membrane routes your Automizy API calls and payloads through Membrane's service, so data will transit/possibly be stored by that third party.
Install Mechanism
No packaged install spec was provided, but SKILL.md instructs users to run `npm install -g @membranehq/cli`. Installing a global npm package is a common pattern but does run third-party code on the host — the package is from the public npm registry (traceable), not an arbitrary URL download.
Credentials
The skill declares no required environment variables or local config paths. It relies on Membrane to handle authentication; this is proportionate to an integration that brokers API calls on behalf of the user. Remember that credentials will be managed by Membrane rather than stored locally.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system privileges. It does not attempt to modify other skills or system-wide agent settings.
Assessment
This skill is instruction-only and uses the Membrane CLI to operate. Before installing: (1) Confirm you trust Membrane (https://getmembrane.com) because API calls and credentials will be routed through and managed by their service; review their privacy/security docs and the @membranehq/cli package on npm/GitHub. (2) Installing a global npm package will run third-party code on your machine — avoid on sensitive or locked-down systems, or install in a sandbox/container. (3) If you need to keep Automizy data entirely within your infrastructure, don't use a third-party proxy — instead use direct Automizy API access (which this skill explicitly discourages). If you operate in a corporate environment, verify with your security team before installing global CLI tools or delegating credentials to an external service.Like a lobster shell, security has layers — review code before you run it.
latestvk973jwks05v9f1tg7amzktj18d843k4b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.