Profitwell
v1.0.2ProfitWell integration. Manage Users, Organizations. Use when the user wants to interact with ProfitWell data.
⭐ 0· 92·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
Name/description ask for ProfitWell integration and the SKILL.md exclusively documents using the Membrane CLI to connect to ProfitWell, discover actions, run them, and proxy requests — all coherent with the stated purpose.
Instruction Scope
Instructions stay within the integration scope (install Membrane CLI, login, connect, list/run actions, proxy requests). They do instruct the user to authenticate via a browser and to route requests through Membrane's proxy, which means data and credentials are handled by Membrane's service — users should be aware their ProfitWell data and tokens will be seen/managed by that third party.
Install Mechanism
There is no automatic install spec in the registry; the SKILL.md recommends running `npm install -g @membranehq/cli`. This is a standard public npm install but requires installing a global package and trusting that package and its publisher.
Credentials
The skill declares no required env vars or local credentials. It explicitly instructs the agent/user to let Membrane manage API keys and auth, which is consistent with the integration model.
Persistence & Privilege
Skill is not always-on, is user-invocable, and allows normal autonomous invocation (platform default). It does not request system-wide config changes or persistent privileges beyond using the Membrane CLI during sessions.
Assessment
This skill is coherent: it tells you to install and use the Membrane CLI to talk to ProfitWell rather than asking for ProfitWell API keys locally. Before using it, verify the @membranehq/cli npm package and the Membrane service (homepage/repository) so you trust the publisher; understand that authenticating will store/manage access on Membrane's servers and that Membrane will proxy requests (so they will see the data and tokens). Install the CLI manually if you choose to proceed, review the permissions requested during the OAuth/connection flow, and consider using a dedicated/limited Membrane tenant for least privilege.Like a lobster shell, security has layers — review code before you run it.
latestvk973tc1jmtwpz3sx292gm4fh45842dg4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.