Dexatel
v1.0.2Dexatel integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Dexatel data.
⭐ 0· 108·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 name/description (Dexatel integration) matches the SKILL.md: it instructs the agent to use the Membrane CLI to manage Dexatel resources. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
All runtime instructions are limited to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Dexatel via Membrane. The doc does not ask the agent to read local files or unrelated environment variables. Note: the instructions will cause data and API calls to be routed through the external Membrane service (including auth flows), which is expected given the stated architecture.
Install Mechanism
No formal install spec in the registry, but SKILL.md instructs installing @membranehq/cli via npm -g. The package is a namespaced npm package (traceable), but a global npm install changes system state and requires privileges — the user should verify the package and prefer isolated environments if concerned.
Credentials
The skill declares no required env vars or secrets. It relies on the user having a Membrane account for auth, which is proportional to the described Membrane-based integration. There are no requests for unrelated credentials.
Persistence & Privilege
always is false and the skill is instruction-only (no code written by the registry). The only persistence/privilege impact comes from the user installing the Membrane CLI (npm global install) and authorizing a Membrane account in a browser; the skill does not request elevated agent-wide privileges.
Assessment
This skill appears coherent: it expects you to install and log into the Membrane CLI and then use Membrane to access Dexatel. Before installing or using it, verify you trust Membrane (@membranehq/cli) and understand that your Dexatel interaction will be proxied through Membrane (they will handle auth and see requests/responses). Prefer installing the CLI in an isolated environment (container, VM, or non-root node environment) if you don't want global npm changes. Be cautious with browser-based login codes in public contexts, and review your Membrane account's active connections/permissions if you want to limit what the agent can access. If you do not want the agent to run these CLI commands autonomously, disable model invocation for the skill or avoid granting it shell/network capabilities.Like a lobster shell, security has layers — review code before you run it.
latestvk9750wdjkcfgh4wmqcv7t7yc81842vn6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.