Dealmachine
v1.0.2DealMachine integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with DealMachine data.
⭐ 0· 80·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 (DealMachine integration) matches the runtime instructions: the skill directs the agent to use the Membrane CLI to authenticate and call DealMachine APIs. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md contains only instructions to install/login to Membrane, create/connect a DealMachine connector, list/run actions, and proxy arbitrary DealMachine API requests via Membrane. It does not instruct reading local secrets, system files, or contacting unexpected endpoints beyond Membrane/DealMachine.
Install Mechanism
This is an instruction-only skill (no automated install), but it tells users to install @membranehq/cli via npm (global install). Installing a global npm package is a normal step but requires user trust in the npm package and elevated permissions on some systems.
Credentials
The skill declares no required env vars and relies on Membrane for auth. This is proportionate, but it means Membrane (and whoever controls that service/account) will see proxied API requests and any data sent — users should trust Membrane and the account used.
Persistence & Privilege
The skill does not request persistent always-on presence, does not modify other skills, and is user-invocable. It relies on the agent invoking the Membrane CLI during use, which is normal for an integration skill.
Assessment
This skill is internally consistent, but before installing/using it: 1) Understand that it routes API calls through the Membrane service and your Membrane account — Membrane will see request payloads and can refresh credentials. Only use if you trust Membrane/getmembrane.com. 2) The SKILL.md asks you to npm install -g @membranehq/cli; installing global npm packages requires appropriate privileges and you should verify the package source on npm/GitHub. 3) Start by listing data (read-only actions) to verify behavior before running state-changing actions (e.g., delete-lead, start-mail-sequence). 4) If you need stronger isolation, run the CLI in a controlled environment (container/VM) or verify Membrane account permissions and minimal scopes. 5) If provenance of the skill (owner/source) matters to you, confirm the repository/homepage and that the published skill matches an official integration.Like a lobster shell, security has layers — review code before you run it.
latestvk978m2m2y3h5cv9ekdc4b3p8m584309p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.