Jenkins

Interact with Jenkins CI/CD server via REST API. Use when you need to trigger builds, check build status, view console output, manage jobs, or monitor Jenkin...

Security Scan

The skill's code and instructions match a Jenkins REST client and appropriately request Jenkins credentials, but the registry metadata does not declare those required environment variables or a primary credential and the source/homepage is missing — an incoherence worth resolving before installing.

Purpose & Capability

The SKILL.md and scripts/jenkins.mjs implement a Jenkins REST client (listing jobs, triggering builds, viewing console, etc.), which is coherent with the skill name and description. However, the registry metadata claims no required env vars or primary credential while the SKILL.md and script require JENKINS_URL, JENKINS_USER, and JENKINS_API_TOKEN — this metadata omission is inconsistent and should be corrected.

Instruction Scope

The runtime instructions and the included script confine actions to interacting with the configured JENKINS_URL via REST API. The instructions do not read unrelated files or credentials beyond the three Jenkins environment variables, nor do they exfiltrate data to unexpected endpoints. API responses are returned as JSON.

Install Mechanism

There is no install script or remote download; the skill is instruction-only with a bundled scripts/jenkins.mjs file. The JavaScript is plain and not obfuscated; it does not fetch or execute additional code from external URLs during install.

Credentials

The script legitimately requires JENKINS_URL, JENKINS_USER, and JENKINS_API_TOKEN to operate, which is proportionate to the stated purpose. The concern is that the registry-level fields (required env vars and primary credential) are not populated, so the skill as published does not advertise that it needs credentials. This mismatch can cause surprise or misconfiguration. Also the skill does not mark JENKINS_API_TOKEN as the primary credential — metadata should reflect that.

Persistence & Privilege

The skill does not request persistent or elevated platform privileges (always is false). It does not modify other skills or system settings and only runs the provided script when invoked.

What to consider before installing

This skill appears to be a straightforward Jenkins REST client, but the registry metadata omits the environment variables and primary credential that the included script actually requires. Before installing, verify the skill's source (homepage/repository) and author since no homepage is provided. If you proceed: provide a Jenkins account/token with least privilege needed (prefer a service user and scoped token), ensure JENKINS_URL points to your trusted Jenkins instance, and consider running the script in an isolated environment first. Ask the publisher to update the metadata to declare JENKINS_URL, JENKINS_USER, and JENKINS_API_TOKEN (and mark the API token as the primary credential) so the requirements are explicit.

Interact with Jenkins CI/CD server through REST API.

Required environment variables

• JENKINS_URL (example: https://jenkins.example.com)
• JENKINS_USER (your Jenkins username)
• JENKINS_API_TOKEN (API token from Jenkins user settings)

List jobs

node {baseDir}/scripts/jenkins.mjs jobs
node {baseDir}/scripts/jenkins.mjs jobs --pattern "deploy-*"

Trigger build

node {baseDir}/scripts/jenkins.mjs build --job "my-job"
node {baseDir}/scripts/jenkins.mjs build --job "my-job" --params '{"BRANCH":"main","ENV":"dev"}'

Check build status

node {baseDir}/scripts/jenkins.mjs status --job "my-job"
node {baseDir}/scripts/jenkins.mjs status --job "my-job" --build 123
node {baseDir}/scripts/jenkins.mjs status --job "my-job" --last

View console output

node {baseDir}/scripts/jenkins.mjs console --job "my-job" --build 123
node {baseDir}/scripts/jenkins.mjs console --job "my-job" --last --tail 50

Stop build

node {baseDir}/scripts/jenkins.mjs stop --job "my-job" --build 123

View queue

node {baseDir}/scripts/jenkins.mjs queue

View nodes

node {baseDir}/scripts/jenkins.mjs nodes

Notes

• URL and credentials are variables by design for cross-environment deployment.
• API responses are output as JSON.
• For parameterized builds, use --params with JSON string.