gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
Overall
score
86%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 1.45xAgent success when using this skill
Validation for skill structure
Discovery
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 follows best practices. It uses third person voice, lists specific capabilities, includes natural trigger terms, and explicitly states both what the skill does and when to use it. The GitLab-specific focus makes it clearly distinguishable from other CI/CD-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'multi-stage workflows', 'caching', 'distributed runners', 'automated testing and deployment'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners') and when ('Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'GitLab CI/CD', 'pipeline', 'caching', 'runners', 'automated testing', 'deployment'. Good coverage of terms a user working with GitLab would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to GitLab specifically, distinguishing it from generic CI/CD or other platforms like GitHub Actions or Jenkins. The 'GitLab' qualifier and specific features like 'distributed runners' create a distinct niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable GitLab CI skill with comprehensive, executable YAML examples covering common pipeline patterns. The main weaknesses are some verbosity in introductory sections and missing validation/rollback guidance for deployment workflows. The structure and progressive disclosure are well-executed.
Suggestions
Remove or condense the 'Purpose' and 'When to Use' sections - these explain obvious use cases Claude already understands
Add explicit validation and rollback steps to deployment workflows (e.g., 'If rollout fails: kubectl rollout undo deployment/my-app')
Trim the best practices list to 5-6 most critical items, or move to a separate reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Purpose' and 'When to Use' that explain obvious use cases Claude would understand. The 10-item best practices list could be more selective. | 2 / 3 |
Actionability | Excellent executable YAML examples throughout - complete pipeline configurations for Docker builds, multi-environment deployments, Terraform, security scanning, and caching. All examples are copy-paste ready with real image tags and commands. | 3 / 3 |
Workflow Clarity | Pipeline stages are clearly sequenced in examples, but lacks explicit validation checkpoints. The Terraform pipeline shows validate->plan->apply but doesn't include error recovery guidance. No feedback loops for failed deployments or rollback procedures. | 2 / 3 |
Progressive Disclosure | Well-organized with clear section headers, references to external files (assets/gitlab-ci.yml.template, references/pipeline-stages.md), and related skills. Content is appropriately structured without deep nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 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.