Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/jenkins-cicd
Jenkins CI/CD pipeline management — monitor builds, trigger pipelines, analyze logs, and track SCM changes for network automation workflows.
5 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 6 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I want to trigger `network-validation` with ENVIRONMENT=prod and DRY_RUN=false. What preliminary step must be completed before asking for operator confirmation?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies executing getJob on network-validation to inspect parameter definitions prior to asking for confirmation | Missed | Passed |
The instructions your model reads when the skill loads.
Manage Jenkins CI/CD pipelines for network automation workflows. This skill provides operational workflows for monitoring job and build status, triggering builds with parameters, analyzing build logs for troubleshooting, and tracking SCM changes across Jenkins projects.
The Jenkins MCP server is an official Jenkins plugin running natively inside Jenkins via Streamable HTTP transport — netclaw connects to it as a remote HTTP client.
Never trigger a build or modify build metadata without explicit operator confirmation. All write operations (triggerBuild, updateBuild) require human-in-the-loop approval per Constitution XIV. Always read current state before proposing any write action (Constitution II — Read-Before-Write).
Monitor Jenkins job status, build results, queue state, and pipeline run history.
List all jobs — Use getJobs with optional pagination (offset, limit) and regex name filter to discover available jobs.
Tool: getJobs
Parameters: { "nameFilter": "deploy-.*", "offset": 0, "limit": 25 }
Get job details — Use getJob with the full job name (supports folder paths like folder1/folder2/job-name) to retrieve job configuration, last build number, and health status.
Tool: getJob
Parameters: { "fullName": "network-automation/deploy-network-config" }
Get build details — Use getBuild with job name and build number to retrieve result, duration, timestamp, parameters, and causes.
Tool: getBuild
Parameters: { "jobFullName": "deploy-network-config", "buildNumber": 42 }
Check queue status — Use getQueueItem to inspect queued build requests — waiting reason, position, estimated start time.
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.