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.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill gitlab-ci-patterns87
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/skillValidation 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 that developers would use, and has an explicit 'Use when...' clause that clearly defines when to select this skill. The GitLab-specific focus makes it highly distinctive from other CI/CD-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'multi-stage workflows', 'caching', 'distributed runners', 'scalable automation', 'optimizing pipeline performance', 'automated testing and deployment'. | 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'. These are terms developers naturally use when working with GitLab pipelines. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to GitLab CI/CD specifically, distinguishing it from other CI/CD tools like GitHub Actions, Jenkins, or CircleCI. The GitLab-specific terminology creates a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 reference with comprehensive, executable YAML examples covering common patterns. The main weaknesses are some verbosity in introductory sections and missing validation/rollback guidance for destructive operations like production deployments and Terraform applies.
Suggestions
Remove or condense the 'Purpose' and 'When to Use' sections - these are self-evident from the skill title and content
Add validation checkpoints for production deployment (e.g., smoke tests, health checks) and rollback procedures if kubectl rollout status fails
Add error recovery guidance for Terraform apply failures, including how to handle partial applies
| 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. For Terraform apply and production deployments (destructive operations), there's no guidance on verifying success or rollback procedures if deployments fail. | 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
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.