Cloudmersive
v1.0.0Cloudmersive integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cloudmersive data.
⭐ 0· 62·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 claims Cloudmersive integration and the SKILL.md consistently instructs using the Membrane CLI to connect to and proxy requests to Cloudmersive. It does not request unrelated credentials or unrelated platform access. Minor inconsistency: the registry metadata lists no required binaries, but the README instructs installing the Node/npm-based @membranehq/cli (so a system with node/npm is implicitly required).
Instruction Scope
Instructions are limited to installing and using the Membrane CLI (login, create connections, list and run actions, and proxy requests). They do not tell the agent to read unrelated local files or environment variables. Caveat: the proxy feature allows sending arbitrary API requests to Cloudmersive via Membrane, which is powerful and can transmit user data to Cloudmersive/Membrane — this is expected for a proxy but worth noting.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing from the public npm registry is a normal approach, but it implicitly requires node/npm to be present. No downloads from untrusted URLs or extract operations are suggested.
Credentials
The skill declares no required environment variables or credentials and relies on Membrane to handle authentication and credential refresh. That is proportionate for an integration that uses a CLI-based connector/proxy. Users should understand that credentials will be managed/stored by Membrane when they run `membrane login`.
Persistence & Privilege
The skill does not request always: true or other elevated persistence. Autonomous invocation is allowed by default (disable-model-invocation: false), which is the platform norm; no additional privilege escalation or cross-skill configuration changes are requested.
Assessment
This skill appears to do what it says: use Membrane CLI to connect to Cloudmersive and run actions. Before installing/using it, confirm you trust Membrane (@membranehq/cli) because it will manage and proxy your Cloudmersive credentials and requests. Ensure node/npm are available if you plan to install the CLI. Review the @membranehq/cli package on npm/GitHub and consider installing it in a controlled environment (or using a container) if you have policy concerns. Be mindful that the proxy feature can send arbitrary data to Cloudmersive via Membrane — avoid sending sensitive information unless you understand how credentials and logs are stored by Membrane and Cloudmersive.Like a lobster shell, security has layers — review code before you run it.
latestvk9710spdwgbdej24pwpc2z2rn983jctm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
