CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/gitlab-ci-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is rich with executable YAML examples but lacks structured workflow guidance with validation checkpoints and inlines everything into one file with no progressive disclosure. Generic instruction boilerplate adds mild verbosity.

Suggestions

Replace the generic 'Instructions' list with a concrete sequenced workflow including validation checkpoints (e.g., lint -> test -> build -> manual approval gate -> deploy -> rollout status verify), since production deploys and terraform apply are destructive/batch operations.

Split large pattern sections (Terraform pipeline, security scanning, dynamic child pipelines) into separate reference files in ./references/ and link to them from SKILL.md to achieve one-level-deep progressive disclosure.

Remove filler sections ('Instructions' generic steps, 'Purpose') that restate what the description already covers, and trim the 'Best Practices' list to the non-obvious items Claude would not already know.

DimensionReasoningScore

Conciseness

Mostly lean with executable YAML examples and minimal over-explanation, though sections like 'Instructions' and 'Purpose' contain generic filler ('Apply relevant best practices') that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready YAML across build, test, deploy, Docker, multi-environment, Terraform, security scanning, caching, and dynamic child pipelines covering the common cases.

5 / 5

Workflow Clarity

The 'Instructions' section lists only generic steps ('Clarify goals', 'Apply best practices', 'validate outcomes') with no explicit sequencing or validation checkpoints for destructive batch operations like production deploys and terraform apply.

3 / 5

Progressive Disclosure

No bundle files exist; all content is inlined into a single monolithic SKILL.md with no external references or one-level-deep navigation, and topical patterns (Docker, Terraform, security) are not split into separate files.

2 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong, clearly stating concrete capabilities and explicit 'Use when' trigger guidance for the GitLab CI/CD domain. It is distinct from related skills and uses natural trigger terms.

DimensionReasoningScore

Specificity

Lists several concrete actions (build multi-stage workflows, caching, distributed runners) tied to a named domain, with minor gaps in coverage around specifics like templating or security scanning.

4 / 5

Completeness

Explicitly answers both 'what' (build pipelines with multi-stage workflows, caching, distributed runners) and 'when' (Use when implementing, optimizing, or setting up testing/deployment) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('implementing GitLab CI/CD', 'optimizing pipeline performance', 'automated testing and deployment'), missing a few common synonyms or file extensions.

4 / 5

Distinctiveness Conflict Risk

Clear GitLab CI/CD niche with distinct triggers (GitLab Runners, GitOps, Kubernetes deploy from GitLab) minimizing conflict risk with adjacent skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.