Bloom Growth
v1.0.0Bloom Growth integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bloom Growth data.
⭐ 0· 25·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the skill tells the agent to use the Membrane CLI to connect to Bloom Growth and manage records. Requiring a Membrane account and network access is coherent with this purpose.
Instruction Scope
SKILL.md only instructs use of the Membrane CLI (login, connect, action list/run, proxy requests). These commands will open a browser for auth and send API requests via Membrane's proxy — expected for this integration, but the user should understand that API calls and data will be routed through Membrane's service.
Install Mechanism
There is no formal install spec in the registry (instruction-only skill), but the README tells users to install @membranehq/cli via npm or use npx. Installing an npm package is reasonable for this functionality; prefer npx or reviewing the @membranehq package on the npm registry before a global install.
Credentials
The skill declares no required env vars or credentials and explicitly recommends not asking users for API keys. Authentication is delegated to Membrane (browser-based login), which is proportionate to the described functionality.
Persistence & Privilege
The skill is instruction-only, has no install-time persistence, and does not request always:true. Model invocation is allowed (platform default) but there is no evidence this skill requests elevated or permanent privileges.
Assessment
This skill is coherent: it uses the Membrane CLI to mediate access to Bloom Growth and does not ask for unrelated credentials. Before installing/using it, review the @membranehq CLI package on npm or use npx to avoid a global install; understand that API requests and data will be proxied through Membrane (so review Membrane's privacy/security docs and your organization's policy). For headless environments follow the documented login flow carefully. If you need a higher assurance level, verify the Membrane organization account and the CLI's source code in the referenced repository before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk97aymveg4rgzwhx5t5393j10984968c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.