Xebialabs
v1.0.0XebiaLabs integration. Manage data, records, and automate workflows. Use when the user wants to interact with XebiaLabs 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
medium confidencePurpose & Capability
The SKILL.md consistently describes interacting with XebiaLabs via the Membrane CLI (discover actions, create connections, proxy requests). Required tools and actions (membrane login, membrane connect, action run, request) directly map to the described purpose.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to XebiaLabs. They do not instruct reading unrelated local files, environment variables, or transmitting data to unexpected endpoints. They do, however, require that the user authenticate to Membrane (browser-based) and grant Membrane access to XebiaLabs via a connector.
Install Mechanism
There is no registry install spec, but the SKILL.md directs users to run `npm install -g @membranehq/cli`. Installing a global npm package is a common but higher‑privilege local install step (may require sudo on some systems). Verify the package provenance on npm/GitHub before installing.
Credentials
The skill requests no environment variables or local credentials; instead it relies on a Membrane account and connector-based auth to XebiaLabs. This is proportionate to the stated function but requires trusting Membrane with delegated access to your XebiaLabs data—ensure you understand what scopes/permissions the connector requests and use least‑privilege accounts where possible.
Persistence & Privilege
The skill is instruction‑only, does not request permanent presence (always: false), and does not modify other skills or system-wide agent settings. Autonomous model invocation is allowed (default) but not combined with other elevated privileges here.
Assessment
This skill appears internally consistent: it tells the agent to use the Membrane CLI to manage XebiaLabs. Before installing or using it, verify the @membranehq/cli package and its GitHub repo (check maintainers, recent releases, and npm download stats), confirm the Membrane privacy/security practices, and avoid using high‑privilege XebiaLabs admin credentials — create a least‑privilege service account for the connector and test in a sandbox. Be aware that `npm install -g` modifies your system environment and may require elevated privileges. If you cannot or do not want to trust Membrane with delegated access, do not use this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk9767kkn463jyyp7r6swzwfqsn846c8n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.