Drimify
v1.0.2Drimify integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Drimify data.
⭐ 0· 87·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
The skill is described as a Drimify integration and its instructions all use the Membrane CLI to interact with Drimify — that matches the stated purpose. Minor inconsistency: registry metadata lists no required binaries, but the SKILL.md requires npm (to install @membranehq/cli) and the membrane CLI itself.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, authenticating via browser, listing/creating connections, running actions, and proxying API requests to Drimify. The doc explicitly warns not to ask users for API keys and does not instruct accessing unrelated files, env vars, or system state.
Install Mechanism
There is no automated install spec in the package (instruction-only). The SKILL.md recommends 'npm install -g @membranehq/cli' (a scoped npm package). Installing a global npm package executes code from the npm registry — a normal but non-trivial action; the package scope appears legitimate (membranehq).
Credentials
The skill declares no required environment variables and does not request secrets. Authentication is performed via the Membrane service/browser flow, which keeps credentials out of local env vars — proportional to the task.
Persistence & Privilege
The skill is instruction-only and not marked always:true. It does not request persistent system-wide privileges or modify other skills' configs; autonomous invocation is allowed (platform default) but not combined with other high-risk factors here.
Assessment
This skill looks coherent for interacting with Drimify via Membrane. Before installing, verify you trust the Membrane project and the @membranehq/cli npm package (check the package page, publisher, and release history). Installing the CLI runs code from npm, so prefer installing on a machine you control (not a sensitive production host) and review the package README/source if you have concerns. Authentication uses a browser flow (no local API keys), and Membrane will proxy API calls to Drimify — be aware that requests and credentials are handled by Membrane's service, so review their privacy/security documentation if that's a concern.Like a lobster shell, security has layers — review code before you run it.
latestvk979vrayebqw1azyhfzzbhv7t58437f1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.