Cloudfill
v1.0.2CloudFill integration. Manage data, records, and automate workflows. Use when the user wants to interact with CloudFill data.
⭐ 0· 80·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 describes CloudFill integration and exclusively instructs the agent to use the Membrane CLI to create connections, list actions, run actions, or proxy requests to CloudFill. Requiring Membrane (and network access) matches the described purpose; there are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
SKILL.md limits runtime instructions to installing/using the @membranehq/cli, authenticating via Membrane, discovering connectors/actions, running actions, and proxying API calls. It does not instruct reading arbitrary local files, harvesting environment variables, or sending data to endpoints outside Membrane/CloudFill.
Install Mechanism
There is no registry install spec, but the instructions tell the user to run `npm install -g @membranehq/cli`. This is a normal installation method for a CLI (package from the public npm registry). It writes a global binary to the system, so verify the package provenance before installing (or use npx/container/local install if you prefer).
Credentials
The skill declares no required environment variables or credentials and explicitly advises not to ask users for API keys. Using Membrane to manage auth is proportionate for this integration. Note that authentication occurs via Membrane's service (server-side), so credentials and proxied requests will be handled by Membrane rather than the local machine.
Persistence & Privilege
The skill is not forced-always and does not request elevated or persistent platform privileges. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill looks coherent but it relies on the Membrane service and its CLI: before installing, verify the @membranehq/cli package and the Membrane service (review the npm package and GitHub repo), and be aware that requests to CloudFill will be proxied through Membrane (so your data and auth live on their service). Consider using npx or a container/local install rather than a global npm install if you want lower system impact. If you need stronger guarantees about data locality or trust, do not connect sensitive accounts until you confirm Membrane's privacy/security posture.Like a lobster shell, security has layers — review code before you run it.
latestvk971a0pdp1g81bsdh5p7cr7nk18428ay
License
MIT-0
Free to use, modify, and redistribute. No attribution required.