Mobivate
v1.0.2Mobivate integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Mobivate data.
⭐ 0· 112·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
The name/description (Mobivate integration) match the instructions: everything centers on using Membrane to call Mobivate APIs and manage Mobivate objects. No unrelated services or permissions are requested.
Instruction Scope
SKILL.md only instructs using the Membrane CLI (login, connect, action list/run, request proxy). It does not ask the agent to read arbitrary local files, harvest environment variables, or transmit data to unexpected endpoints outside Membrane/Mobivate. The headless login flow and proxy usage are documented and expected for this integration.
Install Mechanism
The skill is instruction-only and has no automatic install spec, but it tells users to run 'npm install -g @membranehq/cli' or use npx. This is proportionate for a CLI-based integration, but installing global npm packages requires trusting the package and its publisher.
Credentials
No environment variables, config paths, or API keys are required by the skill. The instructions explicitly state Membrane handles credentials server-side; that is consistent with the described workflow.
Persistence & Privilege
The skill does not request persistent/always-on status, does not modify other skills or system-wide settings, and relies on user-run CLI commands. Autonomous invocation is allowed by platform default but is not combined with additional privileges here.
Assessment
This skill appears coherent: it guides you to install and use the Membrane CLI to connect to Mobivate and avoids asking for API keys. Before installing/use: (1) verify and trust the @membranehq/cli npm package and the Membrane service (you will grant them access to your Mobivate account), (2) be cautious installing global npm packages—prefer using npx or a controlled environment if you do not want a global install, (3) use least-privileged/test accounts when possible, and (4) never paste unrelated secrets into the chat. If you want extra assurance, review the @membranehq/cli package source/release page and Membrane privacy/auth docs before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97dyzjbdtv93xvv0ygqyae2p9842315
License
MIT-0
Free to use, modify, and redistribute. No attribution required.