jenkins-pipeline-intro
Jenkins Pipeline Intro - Auto-activating skill for DevOps Basics. Triggers on: jenkins pipeline intro, jenkins pipeline intro Part of the DevOps Basics skill category.
35
3%
Does it follow best practices?
Impact
95%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/jenkins-pipeline-intro/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak across all dimensions. It reads as auto-generated boilerplate with no substantive content—no concrete actions, no natural trigger terms, and no guidance on when to use the skill. The duplicate trigger term and reliance on category labeling provide almost no value for skill selection.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Explains Jenkins pipeline concepts, creates basic Jenkinsfile configurations, and walks through declarative vs scripted pipeline syntax.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Jenkins pipelines, Jenkinsfiles, CI/CD setup with Jenkins, build automation, or continuous integration basics.'
Remove the duplicate trigger term and replace with varied natural phrases users would actually say, such as 'Jenkins CI/CD', 'Jenkinsfile', 'build pipeline', 'continuous integration', 'pipeline stages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It says 'Jenkins Pipeline Intro' but never describes what the skill actually does—no verbs like 'create', 'configure', 'explain', or 'set up' are present. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause—only a redundant trigger phrase and a category label. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'jenkins pipeline intro' repeated twice. These are not natural phrases a user would say; users are more likely to say things like 'set up a Jenkins pipeline', 'CI/CD', 'Jenkinsfile', 'build pipeline', or 'continuous integration'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Jenkins Pipeline' provides some domain specificity that distinguishes it from generic DevOps skills, but the lack of concrete actions or scope means it could easily overlap with other Jenkins-related or CI/CD skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It contains only auto-generated boilerplate describing what the skill would do without actually providing any Jenkins pipeline knowledge, code examples, or actionable instructions. It fails on every dimension of the rubric.
Suggestions
Add a concrete Jenkinsfile example (Declarative Pipeline syntax) with stages like Build, Test, Deploy that Claude can use as a template.
Include specific Jenkins pipeline commands and syntax (e.g., `pipeline {}`, `agent`, `stages`, `steps`, `post` blocks) with executable examples.
Define a clear workflow for creating a Jenkins pipeline: 1) Create Jenkinsfile, 2) Configure pipeline job, 3) Validate syntax with `jenkins-cli declarative-linter`, 4) Test and iterate.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content about Jenkins pipeline concepts, common patterns, and troubleshooting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual Jenkins pipeline knowledge, commands, or configurations. Every token is wasted on boilerplate. | 1 / 3 |
Actionability | There is zero concrete guidance—no Jenkinsfile examples, no pipeline syntax, no commands, no code snippets. The content only describes itself rather than instructing Claude on how to help with Jenkins pipelines. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for creating, validating, or debugging a Jenkins pipeline. The phrase 'step-by-step guidance' is claimed but never delivered. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain only generic boilerplate. There are no references to detailed files, no structured navigation, and no meaningful content organization—just a flat list of vague descriptions. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.