Proworkflow
v1.0.2ProWorkflow integration. Manage Clients, Staffs, Quotes, Templates, Messages, Groups. Use when the user wants to interact with ProWorkflow data.
⭐ 0· 120·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/description (ProWorkflow integration) matches the SKILL.md: it instructs the agent to use Membrane to list/connect/run actions and proxy requests to ProWorkflow. Required capabilities (network access, a Membrane account) are expected.
Instruction Scope
Instructions are focused on discovering and running actions via the Membrane CLI and using Membrane's proxy for raw API calls. They do not request unrelated files or environment variables, but they do direct API traffic (and authentication) through Membrane's cloud-managed service — a privacy/observability consideration for the user.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing @membranehq/cli via npm -g, which is a reasonable but non-trivial request (global npm install writes system-wide). There is no baked install manifest; users should verify the npm package and trust the vendor before installing globally.
Credentials
The skill declares no required env vars or credentials and advises letting Membrane manage auth (so the skill itself does not ask for API keys). This is proportionate to the stated purpose. Note: authenticating will create a connection managed by Membrane, so credentials are handled server-side by Membrane rather than by the skill.
Persistence & Privilege
always is false and there is no code or installation that persistently modifies agent configuration. The skill is user-invocable and does not request elevated or permanent privileges.
Assessment
This skill appears to do what it says: it relies on the Membrane CLI to talk to ProWorkflow and does not ask for unrelated credentials. Before installing: (1) confirm you trust Membrane/getmembrane.com and review their privacy/terms because API calls and auth tokens will be proxied through their service; (2) verify the npm package (@membranehq/cli) and consider installing in a controlled environment rather than global -g if you prefer; (3) be prepared to complete a browser-based login to create the connection; (4) if you need stricter data control, prefer direct API integration with your own ProWorkflow credentials instead of a third-party proxy.Like a lobster shell, security has layers — review code before you run it.
latestvk97fvcsc0n0wse4d8d4sawybnd843dpf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.