How do I install the Jenkins skill?

Run npx skillmds@latest add rezkam/jenkins in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jenkins safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jenkins?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jenkins free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jenkins?

rezkam (@rezkam) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jenkins by rezkam — Agent Skill

Name: Jenkins
Rating: 4.2 (5 reviews)
Author: rezkam

Jenkins

Interact with Jenkins CI via REST API. Use when checking build status, viewing test failures, reading console output, triggering builds, watching build progress, viewing pipeline stages, listing jobs, or managing the build queue on a Jenkins server.

rezkam Updated Sep 10, 2026

File contents

Jenkins CI

Interact with a Jenkins CI server via its REST API.

Configuration

Run ./setup.sh from the repo root (recommended), or create config files manually:

mkdir -p ~/.boring/jenkins
echo 'https://your-jenkins.example.com' > ~/.boring/jenkins/url
echo 'your-username' > ~/.boring/jenkins/user
echo 'your-api-token' > ~/.boring/jenkins/token
chmod 600 ~/.boring/jenkins/token

Obtain an API token: Log in → Your Username → Configure → API Token → Add new Token → Generate.

Job path format

Paths use / to separate folders:

MyOrg/my-service/main — main branch
MyOrg/my-service/PR-42 — pull request
MyOrg/my-service/feature%2Fmy-branch — URL-encode slashes in branch names

Scripts

Build status

scripts/jenkins-build-status.sh <job-path> [build-number]

Test failures

scripts/jenkins-test-failures.sh <job-path> [build-number] [--full]

--full includes complete stack traces.

Console output

scripts/jenkins-console.sh <job-path> [build-number] [grep-pattern]

Trigger a build

scripts/jenkins-trigger.sh <job-path> [--param KEY=VALUE]...

Watch build progress

scripts/jenkins-watch.sh <job-path> [build-number]

Polls until the build finishes and exits 0 on success, 1 on failure.

Build history

scripts/jenkins-build-history.sh <job-path> [count]

Pipeline stages

scripts/jenkins-stages.sh <job-path> [build-number]

Shows stage names with pass/fail status (requires Pipeline plugin).

List jobs

scripts/jenkins-list-jobs.sh [folder-path] [--depth N]

Build queue

scripts/jenkins-queue.sh

Abort a build

scripts/jenkins-abort.sh <job-path> [build-number]

Raw API

scripts/jenkins-api.sh <endpoint> [curl-options...]

Typical workflow

S=scripts
$S/jenkins-build-status.sh "MyOrg/my-service/PR-42"
$S/jenkins-test-failures.sh "MyOrg/my-service/PR-42"
$S/jenkins-console.sh "MyOrg/my-service/PR-42" lastBuild "ERROR"
$S/jenkins-stages.sh "MyOrg/my-service/PR-42"
$S/jenkins-trigger.sh "MyOrg/my-service/PR-42"
$S/jenkins-watch.sh "MyOrg/my-service/PR-42"

API endpoints reference

Append to job URL:

/api/json — metadata
/lastBuild/api/json — last build
/lastBuild/consoleText — console
/lastBuild/testReport/api/json — test results
/build — trigger (POST)
/buildWithParameters?KEY=VALUE — parameterized trigger (POST)
/lastBuild/wfapi/describe — pipeline stages
/stop — abort (POST)

Query params: tree=field[sub], depth=N

---name: jenkinsdescription: Interact with Jenkins CI via REST API. Use when checking build status, viewing test failures, reading console output, triggering builds, watching build progress, viewing pipeline stages, listing jobs, or managing the build queue on a Jenkins server.---# Jenkins CIInteract with a Jenkins CI server via its REST API.## ConfigurationRun `./setup.sh` from the repo root (recommended), or create config files manually:```bashmkdir -p ~/.boring/jenkinsecho 'https://your-jenkins.example.com' > ~/.boring/jenkins/urlecho 'your-username' > ~/.boring/jenkins/userecho 'your-api-token' > ~/.boring/jenkins/tokenchmod 600 ~/.boring/jenkins/token```Obtain an API token: Log in → Your Username → Configure → API Token → Add new Token → Generate.## Job path formatPaths use `/` to separate folders:- `MyOrg/my-service/main` — main branch- `MyOrg/my-service/PR-42` — pull request- `MyOrg/my-service/feature%2Fmy-branch` — URL-encode slashes in branch names## Scripts### Build status```bashscripts/jenkins-build-status.sh <job-path> [build-number]```### Test failures```bashscripts/jenkins-test-failures.sh <job-path> [build-number] [--full]````--full` includes complete stack traces.### Console output```bashscripts/jenkins-console.sh <job-path> [build-number] [grep-pattern]```### Trigger a build```bashscripts/jenkins-trigger.sh <job-path> [--param KEY=VALUE]...```### Watch build progress```bashscripts/jenkins-watch.sh <job-path> [build-number]```Polls until the build finishes and exits 0 on success, 1 on failure.### Build history```bashscripts/jenkins-build-history.sh <job-path> [count]```### Pipeline stages```bashscripts/jenkins-stages.sh <job-path> [build-number]```Shows stage names with pass/fail status (requires Pipeline plugin).### List jobs```bashscripts/jenkins-list-jobs.sh [folder-path] [--depth N]```### Build queue```bashscripts/jenkins-queue.sh```### Abort a build```bashscripts/jenkins-abort.sh <job-path> [build-number]```### Raw API```bashscripts/jenkins-api.sh <endpoint> [curl-options...]```## Typical workflow```bashS=scripts$S/jenkins-build-status.sh "MyOrg/my-service/PR-42"$S/jenkins-test-failures.sh "MyOrg/my-service/PR-42"$S/jenkins-console.sh "MyOrg/my-service/PR-42" lastBuild "ERROR"$S/jenkins-stages.sh "MyOrg/my-service/PR-42"$S/jenkins-trigger.sh "MyOrg/my-service/PR-42"$S/jenkins-watch.sh "MyOrg/my-service/PR-42"```## API endpoints referenceAppend to job URL:- `/api/json` — metadata- `/lastBuild/api/json` — last build- `/lastBuild/consoleText` — console- `/lastBuild/testReport/api/json` — test results- `/build` — trigger (POST)- `/buildWithParameters?KEY=VALUE` — parameterized trigger (POST)- `/lastBuild/wfapi/describe` — pipeline stages- `/stop` — abort (POST)Query params: `tree=field[sub]`, `depth=N`

Frequently asked questions