devops-jenkins
DevOps Jenkins Agent. Jenkins CI/CD 파이프라인 관리, 빌드 트리거, 로그 조회, Job 관리를 담당합니다. jenkins, 빌드(build), 파이프라인, CI/CD, job 관련 요청 시 사용됩니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill devops-jenkins93
Quality
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/devops-jenkins/SKILL.mdDiscovery
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.
This is a well-crafted skill description that clearly defines its scope (Jenkins CI/CD operations), lists specific capabilities, and provides explicit trigger terms in both Korean and English. The description follows third-person voice and includes a clear 'Use when' clause with natural keywords users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Jenkins CI/CD 파이프라인 관리, 빌드 트리거, 로그 조회, Job 관리' (pipeline management, build triggering, log viewing, job management). | 3 / 3 |
Completeness | Clearly answers both what (파이프라인 관리, 빌드 트리거, 로그 조회, Job 관리) AND when ('jenkins, 빌드(build), 파이프라인, CI/CD, job 관련 요청 시 사용됩니다') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'jenkins, 빌드(build), 파이프라인, CI/CD, job' - covers both Korean and English terms, and common variations users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Jenkins CI/CD with distinct triggers like 'jenkins', 'job', 'build trigger' - unlikely to conflict with other DevOps tools or general coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides clear, actionable MCP tool references for Jenkins operations. The content efficiently covers job management, build operations, and troubleshooting without unnecessary explanation. The main weakness is the lack of explicit validation steps in workflows, particularly for build monitoring where checking build status in a loop until completion would be valuable.
Suggestions
Add explicit validation/feedback loops to the '수동 배포' workflow, such as polling getBuild until status changes from 'BUILDING' to 'SUCCESS' or 'FAILURE'
Include error handling guidance in workflows, e.g., what to do if triggerBuild fails or returns unexpected results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only essential information without explaining what Jenkins or CI/CD is. Every section provides direct, actionable tool calls without unnecessary preamble. | 3 / 3 |
Actionability | All tool calls are concrete and copy-paste ready with clear parameter examples. The syntax is specific and executable, showing both basic and parameterized variations. | 3 / 3 |
Workflow Clarity | Workflows are listed with clear sequences for common tasks like deployment and failure analysis, but lack explicit validation checkpoints or feedback loops for error recovery during build monitoring. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections progressing from basic operations to workflows to troubleshooting. The summary table at the end provides excellent navigation for the complete tool set. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.