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.
90
82%
Does it follow best practices?
Impact
94%
1.18xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 strong skill description that clearly identifies the domain (GitLab CI/CD), lists specific capabilities (multi-stage workflows, caching, distributed runners), and provides explicit trigger guidance via a 'Use when' clause. It uses proper third-person voice and includes natural keywords that users would employ when seeking help with GitLab pipelines.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building multi-stage workflows, caching, distributed runners, and scalable automation. These are concrete, actionable capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners) and 'when' (implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'GitLab CI/CD', 'pipeline', 'caching', 'runners', 'automated testing', 'deployment', 'pipeline performance'. These cover common terms a user would naturally use when seeking this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to GitLab CI/CD specifically, with distinct triggers like 'GitLab CI/CD', 'distributed runners', and 'multi-stage workflows' that distinguish it from generic CI/CD or other platform-specific pipeline skills (e.g., GitHub Actions, Jenkins). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable GitLab CI/CD patterns covering a broad range of use cases. Its main weaknesses are the monolithic structure that could benefit from progressive disclosure, some unnecessary introductory content, and missing validation/error-recovery steps for destructive deployment operations. The code examples are the strongest aspect, being complete and production-ready.
Suggestions
Add explicit validation and rollback steps to deployment workflows (e.g., health checks after kubectl apply, rollback commands on failure) to improve workflow clarity for destructive operations.
Split advanced patterns (Terraform pipeline, security scanning, dynamic child pipelines) into separate referenced files, keeping SKILL.md as a concise overview with the basic pipeline and links to detailed guides.
Remove the 'Purpose', 'When to Use', and generic 'Best Practices' sections—these add little value for Claude and consume tokens on information that's either obvious or too vague to be actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('Comprehensive GitLab CI/CD pipeline patterns...', 'Purpose', 'When to Use' sections) and the Best Practices section is a generic list of advice Claude already knows. However, the code examples themselves are lean and well-structured without excessive explanation. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready YAML configurations for multiple real-world scenarios including basic pipelines, Docker builds, multi-environment deployments, Terraform pipelines, security scanning, caching strategies, and dynamic child pipelines. Each example is complete and specific. | 3 / 3 |
Workflow Clarity | The Terraform pipeline shows a clear validate→plan→apply sequence with manual gates, and deployments use rollout status checks. However, there are no explicit validation/verification steps or error recovery feedback loops for the deployment workflows, which involve potentially destructive operations (kubectl apply, terraform apply). | 2 / 3 |
Progressive Disclosure | The content is a long monolithic file (~200 lines of YAML examples) that could benefit from splitting advanced patterns (Terraform, security scanning, dynamic pipelines) into separate referenced files. The Related Skills section provides some cross-references, but the main content lacks clear navigation structure for its substantial length. | 2 / 3 |
Total | 9 / 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.
- Repository
- wshobson/agents
- Commit
70444e5
- 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.