Jenkins X
v1.0.2Jenkins X integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jenkins X data.
⭐ 0· 82·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.md and commands align with a Jenkins X integration: it instructs installing the Membrane CLI, creating a Membrane connection to Jenkins X, listing and running actions, and proxying API requests. Nothing requested (no env vars, no config paths) is inconsistent with that purpose.
Instruction Scope
Runtime instructions stay within the expected scope: installing and using the Membrane CLI, performing browser-based login, creating connections, listing actions, running actions, and proxying Jenkins X API calls. The skill does not instruct reading unrelated local files or env vars. Note: using Membrane means requests and credentials are proxied through a third party (Membrane).
Install Mechanism
There is no packaged install spec; the doc recommends `npm install -g @membranehq/cli`. Installing a third-party CLI from npm is common and expected here, but it requires trust in the @membranehq package and modifies the system PATH when installed globally.
Credentials
The skill declares no required environment variables or credentials. It explicitly delegates auth to Membrane and advises not to ask users for API keys. This is proportionate for a connector that relies on a third-party proxy/service to manage credentials.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It is user-invocable and allows normal autonomous invocation (platform default). There is no instruction to modify other skills or system-wide configuration.
Assessment
This skill looks coherent, but you’re delegating access to Jenkins X through a third party (Membrane). Before installing: verify the @membranehq npm package and the Membrane project (homepage, repo, publisher), review Membrane’s privacy/auth handling and corporate policy about routing CI/CD access through external services, consider installing the CLI locally or in an isolated environment rather than globally, and limit the Jenkins X account/permissions used for the connection to the minimum required. If you need stronger guarantees, inspect the Membrane CLI source code or use an alternative integration under your direct control.Like a lobster shell, security has layers — review code before you run it.
latestvk97aj0qcnd77kpswz102yq3d3s843ss1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.