Prove
v1.0.0Prove integration. Manage data, records, and automate workflows. Use when the user wants to interact with Prove data.
⭐ 0· 31·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 name/description (Prove integration) matches the instructions (use Membrane CLI to connect to Prove, list actions, run actions, and proxy requests). It does not request unrelated environment variables or binaries.
Instruction Scope
SKILL.md only instructs the agent/user to install and use the Membrane CLI, authenticate via browser or headless flow, create/list connections, run actions, and proxy API requests. These steps are within the scope of interacting with Prove data. It explicitly advises against asking users for API keys and relies on Membrane for auth and credential refresh.
Install Mechanism
The registry contains no automated install spec (lowest platform risk). The skill instructs the user to run `npm install -g @membranehq/cli` manually. Installing a third‑party CLI globally is a normal instruction but carries the usual user-side risks (global npm install requires appropriate local permissions and you should trust the package and its publisher).
Credentials
The skill declares no required env vars or credentials and relies on Membrane to manage auth. This is proportionate to its purpose. The main external requirement is a Membrane account and network access.
Persistence & Privilege
always:false and default model invocation are appropriate. The skill does not request persistent presence or system-wide configuration changes.
Assessment
This skill is coherent and delegates authentication to the Membrane service; before using it, confirm you trust Membrane (review https://getmembrane.com and the @membranehq/cli package/repository), because API requests and Prove data will be proxied through Membrane. Installing the CLI requires running `npm install -g`, which is a local change — verify the package source and, if possible, inspect the CLI code or use a scoped/local install. When you connect a Prove account via the browser flow, check the granted scopes and use a test account or least-privilege credentials if you are unsure. If you require stricter privacy, consider whether routing traffic through Membrane is acceptable for your data policy.Like a lobster shell, security has layers — review code before you run it.
latestvk97fce9w5naf081pbf589nx8ts847aty
License
MIT-0
Free to use, modify, and redistribute. No attribution required.