Celoxis
v1.0.2Celoxis integration. Manage data, records, and automate workflows. Use when the user wants to interact with Celoxis data.
⭐ 0· 113·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 integrate with Celoxis and its SKILL.md consistently instructs the agent to use the Membrane CLI to discover connectors, create connections, run pre-built actions, or proxy raw Celoxis API requests. Required capabilities (network access, a Membrane account, installing @membranehq/cli) match the stated purpose.
Instruction Scope
Runtime instructions stay within the Celoxis integration scope (login via Membrane, list/connect actions, run actions, or proxy API calls). However, the Membrane proxy will transmit requests and injected auth to the external Membrane service — you must trust that service with the data and credentials it proxies.
Install Mechanism
No built-in install spec (instruction-only). It recommends installing the Membrane CLI via npm (-g), which is reasonable for the described workflow but carries the usual npm-global risks (runs package code on install). Verify the package name/maintainer and prefer installing in a controlled environment if you have security concerns.
Credentials
The skill declares no environment variables or local secrets and explicitly tells users not to paste API keys (Membrane manages auth server-side). This is proportionate, but centralizing credential handling in Membrane means trusting that external service with access to Celoxis resources.
Persistence & Privilege
The skill is not always-enabled and has no install footprint beyond the user's optional Membrane CLI installation. It does allow agent invocation (default), which is expected for skills; there is no indication it requests elevated system privileges or modifies other skills.
Assessment
This skill is internally consistent with a Membrane-based Celoxis integration, but before installing: (1) verify the @membranehq/cli package and publisher on npm and prefer installing in a sandbox or VM if you worry about npm-global installs; (2) understand that authentication and proxied requests go through Membrane — you are trusting that external service with access to your Celoxis data and credentials; (3) review Membrane's privacy/security docs and the referenced GitHub repo if you need more assurance; and (4) restrict agent permissions if you don't want autonomous agents to query or modify Celoxis data without explicit approval.Like a lobster shell, security has layers — review code before you run it.
latestvk97cp6qfp2nfkk62cbd8d9fzz184336q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.