Maximizer
v1.0.0Maximizer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Maximizer data.
⭐ 0· 66·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 and description match the instructions: the SKILL.md exclusively documents using the Membrane CLI to connect to and operate on Maximizer CRM. There are no unrelated credential requests or unrelated binaries required.
Instruction Scope
Instructions are scoped to installing and using the Membrane CLI (login, create connections, list actions, run actions, and proxy requests). The document does not instruct reading unrelated files, accessing other environment variables, or transmitting data to unexpected endpoints beyond Membrane/Maximizer.
Install Mechanism
This skill is instruction-only (no install spec), but the SKILL.md tells users to run `npm install -g @membranehq/cli` or use `npx @membranehq/cli@latest`. That is a user-executed package installation which is expected for this integration but carries routine supply-chain and privilege considerations (global npm install requires elevated permissions on some systems; running `npx ...@latest` fetches and executes remote code).
Credentials
The skill declares no required environment variables, credentials, or config paths. The guidance explicitly advises letting Membrane handle API keys and not asking users for secrets, which is consistent with its design.
Persistence & Privilege
Skill is not always-enabled and does not request persistent system-wide configuration. It's user-invocable and allows normal autonomous invocation by the agent (platform default) — appropriate for a connector skill.
Assessment
This skill is internally consistent and appears to do what it claims, but it depends on the third-party Membrane service and its CLI. Before installing or running the CLI: (1) verify you trust getmembrane.com and the @membranehq/cli package (check the package source on GitHub and the npm publisher), (2) prefer installing a specific audited version rather than `@latest` to reduce supply-chain risk, (3) avoid running global installs on sensitive machines without review (global npm installs may require elevated privileges), and (4) remember Membrane will hold/mediate your Maximizer credentials server-side — only proceed if you’re comfortable entrusting them to that service.Like a lobster shell, security has layers — review code before you run it.
latestvk97fs0av068z8gs8bec7wht2md845r6g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.