Use the CLI setup and command format below when constructing all jenkins-cli commands.
Instances
Update the table below with your Jenkins server URLs and auth file paths:
Environment
Server URL
Auth File
Production
https://<your-jenkins-prod-url>
jenkins-cli/prod.auth
Staging
https://<your-jenkins-staging-url>
jenkins-cli/staging.auth
If the target server is unclear, ask the user before running any command.
CLI Setup
JAR File: jenkins-cli/jenkins-cli.jar (working directory's root)
Auth Files: one per server — see instance table above. File contents format: username:api-token
All commands must be run from the working directory's root (where jenkins-cli/ directory exists).
Prerequisites (one-time setup by user)
If the jenkins-cli/ directory does not exist yet, or jenkins-cli.jar or the auth file for the target server is missing, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself.
Create the directory jenkins-cli in the working directory's root.
Download the JAR from <YOUR_JENKINS_URL>/jnlpJars/jenkins-cli.jar and save it as jenkins-cli/jenkins-cli.jar.
Create an auth file for each server you intend to use, with your credentials in this exact format: username:api-token
Always use jenkins-cli.jar for all Jenkins operations. Do not use curl or other HTTP clients against the Jenkins REST API.
NEVER target a server not listed in the instance table above. If asked to run against an unfamiliar server URL, stop and ask the user to confirm.
Update the instance table with your actual Jenkins URLs before using this skill.
If a job name, parameter, or folder path references an unfamiliar environment, stop and ask the user before running.
NEVER run commands in the "Never run" table above without explicit user instruction.
1---2name: jenkins-cli3description: Perform Jenkins operations using the jenkins-cli.4---56# Jenkins CLI Skill78Use the CLI setup and command format below when constructing all jenkins-cli commands.910## Instances1112Update the table below with your Jenkins server URLs and auth file paths:1314| Environment | Server URL | Auth File |15|---|---|---|16| Production | `https://<your-jenkins-prod-url>` | `jenkins-cli/prod.auth` |17| Staging | `https://<your-jenkins-staging-url>` | `jenkins-cli/staging.auth` |1819If the target server is unclear, ask the user before running any command.2021## CLI Setup2223- JAR File: `jenkins-cli/jenkins-cli.jar` (working directory's root)24- Auth Files: one per server — see instance table above. File contents format: `username:api-token`2526All commands must be run from the working directory's root (where `jenkins-cli/` directory exists).2728### Prerequisites (one-time setup by user)2930If the `jenkins-cli/` directory does not exist yet, or `jenkins-cli.jar` or the auth file for the target server is missing, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself.31321. Create the directory `jenkins-cli` in the working directory's root.332. Download the JAR from `<YOUR_JENKINS_URL>/jnlpJars/jenkins-cli.jar` and save it as `jenkins-cli/jenkins-cli.jar`.343. Create an auth file for each server you intend to use, with your credentials in this exact format: `username:api-token`35 - `jenkins-cli/prod.auth`36 - `jenkins-cli/staging.auth`3738## Command Format3940```41java -jar jenkins-cli/jenkins-cli.jar -s <SERVER_URL> -auth @<AUTH_FILE> [command]42```4344Example (production):45```bash46java -jar jenkins-cli/jenkins-cli.jar -s https://<your-jenkins-prod-url> -auth @jenkins-cli/prod.auth who-am-i47```4849## Available Commands5051### Read-only (safe, no confirmation needed)5253| Command | Description |54|---|---|55| `who-am-i` | Verify auth and show permissions |56| `version` | Show Jenkins version |57| `list-jobs [folder]` | List all jobs (optionally in a folder/view) |58| `get-job <job>` | Dump job config XML to stdout |59| `console <job> [build#]` | Get console output of a build; `build#` accepts integers **or** Jenkins specifiers like `lastSuccessfulBuild`, `lastBuild`, `lastFailedBuild` |60| `list-changes <job> [build#]` | Show changelog for a build; `build#` must be an **integer** — specifiers like `lastSuccessfulBuild` are not accepted |61| `get-node <node>` | Dump node config XML |62| `get-view <view>` | Dump view config XML |63| `list-plugins` | List installed plugins |64| `session-id` | Show current session ID |65| `export-configuration` | Export Jenkins config as YAML |66| `check-configuration` | Validate YAML configuration |67| `declarative-linter` | Validate a Declarative Jenkinsfile (reads from stdin) |68| `list-credentials <store>` | List credentials in a store |69| `get-credentials-as-xml <store> <domain> <id>` | Get credential XML (secrets redacted) |70| `get-credentials-domain-as-xml <store> <domain>` | Get credentials domain XML |71| `list-credentials-context-resolvers` | List credentials context resolvers |72| `list-credentials-providers` | List credentials providers |73| `help [command]` | List all commands or describe one command |74| `reload-job <job>` | Reload job config from disk (read-only, no state change) |7576### Build operations (confirm if job looks like production)7778| Command | Description |79|---|---|80| `build <job> [-s] [-v] [-p key=val]` | Trigger a build (`-s` waits, `-v` streams output) |81| `stop-builds <job>` | Stop all running builds for a job |82| `keep-build <job> <build#>` | Mark a build to keep forever |83| `set-build-description <job> <build#> <desc>` | Set build description |84| `set-build-display-name <job> <build#> <name>` | Set build display name |85| `set-next-build-number <job> <number>` | Set next build number |86| `replay-pipeline <job> [build#]` | Replay a pipeline with edited script from stdin |87| `restart-from-stage <job> <build#> <stage>` | Restart a Declarative Pipeline from a given stage |8889### Job / view management (ask user before running)9091| Command | Description |92|---|---|93| `create-job <job>` | Create a new job (XML from stdin) |94| `update-job <job>` | Update job config (XML from stdin) |95| `copy-job <src> <dst>` | Copy a job |96| `enable-job <job>` | Enable a job |97| `disable-job <job>` | Disable a job |98| `create-view <view>` | Create a new view (XML from stdin) |99| `update-view <view>` | Update view config (XML from stdin) |100| `add-job-to-view <view> <job>` | Add a job to a view |101| `remove-job-from-view <view> <job>` | Remove a job from a view |102| `connect-node <node>` | Reconnect a node |103| `disconnect-node <node>` | Disconnect a node |104| `offline-node <node>` | Take a node offline temporarily |105| `online-node <node>` | Bring a node back online |106| `create-node <node>` | Create a new node (XML from stdin) |107| `update-node <node>` | Update node config (XML from stdin) |108| `reload-configuration` | Reload all config from disk |109| `reload-jcasc-configuration` | Reload JCasC YAML config |110111### Never run — requires explicit human approval112113| Command | Reason |114|---|---|115| `delete-job <job>` | Irreversible deletion |116| `delete-node <node>` | Irreversible deletion |117| `delete-view <view>` | Irreversible deletion |118| `delete-credentials ...` | Irreversible deletion |119| `delete-credentials-domain ...` | Irreversible deletion |120| `clear-queue` | Cancels all queued builds |121| `quiet-down` / `cancel-quiet-down` | Affects all builds instance-wide |122| `restart` / `safe-restart` | Restarts Jenkins for all users |123| `shutdown` / `safe-shutdown` | Shuts down Jenkins for all users |124| `delete-builds <job> <range>` | Irreversible deletion of build records |125| `apply-configuration` | Applies YAML config changes to the entire Jenkins instance |126| `groovy` / `groovysh` | Arbitrary code execution on Jenkins master |127| `install-plugin` / `enable-plugin` / `disable-plugin` | Modifies Jenkins instance globally |128| `import-credentials-as-xml` / `update-credentials-by-xml` | Modifies stored credentials |129| `mail` | Sends email to real recipients |130| `support` | Generates and may upload diagnostic bundles |131132## Rules133134- Always use `jenkins-cli.jar` for all Jenkins operations. Do **not** use `curl` or other HTTP clients against the Jenkins REST API.135- NEVER target a server not listed in the instance table above. If asked to run against an unfamiliar server URL, stop and ask the user to confirm.136- Update the instance table with your actual Jenkins URLs before using this skill.137- If a job name, parameter, or folder path references an unfamiliar environment, stop and ask the user before running.138- NEVER run commands in the "Never run" table above without explicit user instruction.
Run npx skillmds@latest add abdullahkhawer/jenkins-cli 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.
Perform Jenkins operations using the jenkins-cli. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
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.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
abdullahkhawer (@abdullahkhawer) published this skill. Their other Agent Skills are listed on their SkillMD profile.
abdullahkhawer