Comprehensive toolkit for validating, linting, testing, and automating Jenkinsfile pipelines (both Declarative and Scripted). Use this skill when working with Jenkins pipeline files, validating pipeline syntax, checking best practices, debugging pipeline issues, or working with custom plugins.
74
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill instructs the agent to read Jenkinsfiles, detect and report hardcoded credentials, and provide inline code snippets from those files—behavior that can require reproducing secret values verbatim (exfiltration risk).
[REDACTED]
secret · 3 sites
The skill instructs the agent to read Jenkinsfiles (line 137), scan for hardcoded credentials (line 14), and then provide inline fix suggestions with corrected code snippets (line 151) — this workflow can cause the agent to reproduce detected secret values verbatim in its response.
SKILL.md
14
**Both types**: Hardcoded credential detection, controller-heavy operations (JsonSlurper, HttpRequest), variable declarations, plugin-specific step validation.
SKILL.md
137
2. **Optionally read the Jenkinsfile** using the Read tool if you need to:
SKILL.md
151
5. **Provide inline fix suggestions** when errors are found (include corrected code snippets directly in the response)
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The SKILL.md "Plugin Documentation Lookup" workflow explicitly instructs Claude to look up unknown plugins using Context7 and, if that fails, to perform WebSearch and consult public sites like https://plugins.jenkins.io/—which requires fetching and interpreting untrusted public web content that can influence validation decisions.
plugins.jenkins.io
domain · 4 sites
The Plugin Documentation Lookup workflow (lines 102-116) explicitly instructs using WebSearch with fallback to https://plugins.jenkins.io/ for unknown plugins, fetching and interpreting untrusted public web content that can influence validation decisions.
SKILL.md
111
- Official source: <https://plugins.jenkins.io/>
158
- Jenkins Plugins: <https://plugins.jenkins.io/>
references/common_plugins.md
750
3. **Official Plugins**: <https://plugins.jenkins.io/>
756
- [Jenkins Plugins Index](https://plugins.jenkins.io/)