Xeditor
v1.0.0Xeditor integration. Manage data, records, and automate workflows. Use when the user wants to interact with Xeditor data.
⭐ 0· 58·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's stated purpose (Xeditor integration) matches the instructions (use Membrane to connect to Xeditor). Minor inconsistency: the registry metadata lists no required binaries, but the runtime instructions assume the user can install and run the Membrane CLI (npm and node present) — the skill should have declared that dependency.
Instruction Scope
SKILL.md instructs only to install and use the Membrane CLI, create a connection, run pre-built actions, or proxy API calls through Membrane. It does not instruct the agent to read local files, environment variables, or unrelated credentials. It does require network access and interactive/browser-based authentication, which is expected for this integration.
Install Mechanism
There is no automated install spec (skill is instruction-only). The doc tells the user to run 'npm install -g @membranehq/cli' — an ordinary, traceable public npm package install. This is reasonable but the skill could be clearer in metadata about required client tooling.
Credentials
The skill requests no environment variables, secrets, or config paths. It explicitly instructs not to ask users for API keys and to let Membrane manage credentials server-side, which is proportionate to the stated purpose.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or to modify other skills. It relies on the Membrane service for auth and proxying; no local persistent presence is required.
Assessment
This skill appears coherent: it expects you to install and use the Membrane CLI and to authenticate via your browser to create a connection to Xeditor. Before installing or using it: (1) confirm you are comfortable installing a global npm package (@membranehq/cli) from the npm registry; (2) verify the Membrane project and its privacy/security posture (what scopes the Xeditor connection will have, what data Membrane will see); (3) be aware that you'll perform browser-based login that grants Membrane access to Xeditor on your behalf; and (4) note the minor metadata mismatch — the skill should declare the CLI/npm requirement. If any of those are unacceptable, do not install or connect production accounts.Like a lobster shell, security has layers — review code before you run it.
latestvk970y1nybh6wrt219qqq6ee61s8449zs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.