CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/jenkinsfile-test-stages

Configures Jenkins declarative pipeline test stages - `Jenkinsfile` with stages, parallel + per-agent execution, post-actions (always / failure / success), pipeline-junit-plugin for test reports, lockable resources for shared infra. Use for Jenkins-based CI (common in enterprise / regulated environments).

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and highly actionable with executable Jenkinsfiles and a well-structured reference split. Its one weak spot is workflow clarity: the build sequence lacks an explicit validation checkpoint before relying on the pipeline.

Suggestions

Add a validation step to the "How to use" sequence — e.g., lint the Jenkinsfile with the Jenkins declarative linter (`jenkins-cli declarative-linter`/replay) or run a trial build and confirm the Jenkins UI shows green before committing.

Turn the worked example into a verify→fix→retry loop by noting how to read the JUnit report / `post { failure }` feedback to triose a broken stage.

Explicitly mark the "For new projects in 2026+" guidance as contextual so the date does not read as a fragile deprecation schedule.

DimensionReasoningScore

Conciseness

The body is code-forward and lean — two full Jenkinsfiles, a retry snippet, an anti-patterns table, and tight reference pointers — with only brief, justified domain orientation (declarative syntax bullets) rather than verbose explanation of concepts Claude already knows.

3 / 3

Actionability

Provides complete, copy-paste-ready Groovy examples (basic Jenkinsfile, Docker agent, retry) plus concrete per-anti-pattern fixes, fully executable rather than pseudocode or vague direction.

3 / 3

Workflow Clarity

The "How to use" section gives a clear numbered 7-step sequence with an anti-patterns review checkpoint, but no explicit validation/verification step (e.g., linting the Jenkinsfile or running a trial build) that the level-3 anchor calls for, so it sits above the unsequenced level 1 yet below the validation-with-feedback-loop level 3.

2 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep references to three verified real files (parallel-and-matrix.md, post-actions.md, environment-and-triggers.md) that contain code directly with no nested see-also chains, matching the clear-overview anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and explicitly scoped with a "Use for" clause, cleanly answering both what the skill does and when to use it. Its Jenkins-specific framing keeps conflict risk with sibling CI skills low.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Configures Jenkins declarative pipeline test stages", "parallel + per-agent execution", "post-actions (always / failure / success)", "pipeline-junit-plugin for test reports", "lockable resources" — in third person, matching the multi-action anchor rather than the vague single-action level 2.

3 / 3

Completeness

Explicitly answers both what (configures stages, parallel execution, post-actions, junit, locks) and when via the "Use for Jenkins-based CI (common in enterprise / regulated environments)" clause, mirroring the good example pattern with an explicit trigger.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — "Jenkins", "Jenkinsfile", "test stages", "test reports", "CI", "enterprise / regulated environments" — giving good coverage rather than the jargon-only or partial level 1/2.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Jenkins-specific niche ("Jenkins-based CI") distinct from the GitHub Actions / GitLab CI alternatives named in the body, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents