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.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

A concrete, code-rich patterns catalog with strong actionability but padded generic instructional sections and no validation feedback loops for destructive operations. All content lives inline in a long SKILL.md with no bundle references, limiting progressive disclosure.

Suggestions

Remove the generic Instructions/Purpose bullets ("Clarify goals...", "Apply relevant best practices...", "Provide actionable steps and verification") which restate knowledge Claude already has, and replace with skill-specific guidance.

Add explicit validation checkpoints for destructive operations, e.g. a `terraform plan` review gate before `apply` and a post-deploy `kubectl rollout status` verify-and-rollback step, to lift workflow clarity.

Move the larger example pipelines (Terraform, multi-environment deployment) into reference files under references/ and link to them from SKILL.md so the main file stays a concise overview.

DimensionReasoningScore

Conciseness

The bulk is lean, executable YAML, but generic boilerplate sections ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes", "Provide actionable steps and verification", and the Purpose section) restate what Claude already knows; it is not level 3 because those padded instructional lines do not earn their tokens, and not level 1 because the code examples are directly useful rather than concept-explaining filler.

2 / 3

Actionability

Multiple complete, copy-paste-ready YAML pipelines are provided (basic build/test/deploy, Docker build/push, multi-environment deployment, Terraform, security scanning, caching, child pipelines) with real variables and commands; it is not level 2 because these are fully executable, not pseudocode or partial guidance.

3 / 3

Workflow Clarity

Content is organized by pattern rather than a sequenced workflow, and the generic Instructions steps lack validation checkpoints; although production deploys and Terraform apply use `when: manual` gates, there is no explicit validate-then-proceed feedback loop for these destructive operations, capping the score at 2 per the batch/destructive guideline.

2 / 3

Progressive Disclosure

The file is well-sectioned with no nested references, but at ~278 lines it is a monolithic catalog whose large per-pattern YAML blocks could live in separate reference files; it is not level 3 because the inline content that could be split is kept entirely in SKILL.md, and not level 1 because organization is clean and shallow rather than a wall of text with deep reference chains.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong, third-person description that states concrete capabilities and provides an explicit 'Use when' trigger clause scoped to GitLab CI/CD. It is specific, complete, and clearly distinguishable from adjacent CI/CD skills.

DimensionReasoningScore

Specificity

"Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners" lists several concrete actions (multi-stage workflows, caching, distributed runners) rather than vague language, matching the level-3 anchor; it is not level 2 because the actions are specific and plural rather than a single domain/action pair.

3 / 3

Completeness

It answers "what" (build pipelines with multi-stage workflows, caching, runners) and "when" via an explicit "Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment" clause, satisfying the level-3 anchor; it is not level 2 because the trigger guidance is explicit rather than implied.

3 / 3

Trigger Term Quality

Natural user-facing terms appear — "GitLab CI/CD", "pipelines", "pipeline performance", "automated testing", "deployment" — covering common phrasings a user would say; it is not level 2 because both the core term and its variants are present rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

The GitLab-specific scope ("GitLab CI/CD", "GitLab Runners") carves a clear niche unlikely to trigger for GitHub Actions or generic CI skills; it is not level 2 because the GitLab qualifier makes overlap with sibling skills low.

3 / 3

Total

12

/

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.

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.