Sellix
v1.0.2Sellix integration. Manage Deals, Persons, Organizations, Leads, Projects, Activities and more. Use when the user wants to interact with Sellix data.
⭐ 0· 128·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 (Sellix integration) match the runtime instructions: everything is about using the Membrane CLI to access Sellix resources. Required network access and a Membrane account are reasonable and proportional to the stated purpose.
Instruction Scope
SKILL.md limits runtime behavior to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to the Sellix API. It does not instruct reading unrelated files, exporting env vars, or contacting endpoints other than through Membrane. Headless login and browser-based auth flows are documented and expected for this flow.
Install Mechanism
There is no packaged install spec; the doc instructs users to install @membranehq/cli via `npm install -g`. This is expected for a CLI-based integration but has the usual caveats for global npm installs (writes to disk, requires permissions). The package is on npm under @membranehq which should be audited/verified by the user before installing.
Credentials
The skill declares no required env vars or credentials and explicitly tells the user not to supply API keys locally. All authentication is delegated to Membrane's connection flow, which is proportional to the functionality. The user must trust Membrane to handle credentials server-side.
Persistence & Privilege
No special persistence is requested (always: false). The skill does not request to modify other skills or system-wide settings. Autonomous invocation is allowed by platform default but the skill itself does not escalate privileges.
Assessment
This skill is coherent: it uses the Membrane CLI/service to access Sellix and does not ask for unrelated secrets. Before installing/using: (1) confirm you trust Membrane (check the @membranehq npm package, the GitHub repo, and the company/site), (2) be aware `npm install -g` will create a global binary and requires appropriate permissions, and (3) understand that Membrane will hold and refresh Sellix credentials server-side — you should review their security/privacy policy and the connector's requested scopes. If you need to run this in a locked-down environment, verify whether Membrane's headless login flow and CLI are acceptable for your security posture.Like a lobster shell, security has layers — review code before you run it.
latestvk979zhdak5z1e9v9fxjjf784sh843fdn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.