Extensiv Integration Manager
v1.0.2Extensiv Integration Manager integration. Manage data, records, and automate workflows. Use when the user wants to interact with Extensiv Integration Manager...
⭐ 0· 135·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 claims to manage Extensiv Integration Manager via the Membrane CLI and all instructions center on installing and using @membranehq/cli and Membrane commands to list connections, run actions, and proxy API requests — this is coherent with the stated purpose.
Instruction Scope
SKILL.md limits runtime actions to installing the Membrane CLI, running membrane login, connection discovery, action listing/running, and proxied requests to Extensiv endpoints. It does not instruct reading unrelated system files or exfiltrating data to unknown endpoints.
Install Mechanism
There is no embedded install spec in the skill bundle; the instructions advise a standard global npm install of @membranehq/cli. This is a common, traceable install method (npm) and appropriate for a CLI-based integration.
Credentials
The skill requests no environment variables, no config paths, and no credentials in its bundle. It expects the user to authenticate with Membrane via interactive login — which is proportionate to accessing third-party SaaS resources.
Persistence & Privilege
The skill is instruction-only, not always-enabled, and does not request persistent system privileges or modify other skills. Autonomous invocation is allowed by platform default but the skill itself does not request elevated persistence.
Assessment
This skill is an instruction-only wrapper that relies on the official Membrane CLI to access Extensiv Integration Manager. Before installing or running commands: (1) verify the npm package name (@membranehq/cli) and publisher on the npm registry and inspect its source (the repository link is included in SKILL.md); (2) be prepared to authenticate via a browser—Membrane will store credentials locally to call Extensiv on your behalf; (3) understand that running actions or proxied requests will operate on your Extensiv account data, so limit the Membrane account's permissions to the minimum needed; and (4) avoid global installs on systems you don't control or audit, or install into a controlled environment (container/VM) if you need extra isolation.Like a lobster shell, security has layers — review code before you run it.
latestvk971nsfgzr8s04f0898qjma599843s0y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.