CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/gitlab-ci-test-jobs

Configures GitLab CI/CD test stages - `.gitlab-ci.yml` with parallel matrix, artifact reports (junit, coverage), services (postgres, redis), needs / dependencies between jobs, only/except + rules for trigger filtering, retry policy. Use when the project hosts on GitLab and the team wants idiomatic GitLab CI patterns.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

80%

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

A highly actionable, token-efficient catalog of GitLab CI patterns with complete code examples and a useful anti-patterns table. It loses points only on workflow clarity and progressive disclosure, where it lacks an explicit validation checkpoint and keeps everything in one file rather than offloading advanced material to referenced files.

Suggestions

Add an explicit verification step to the workflow — e.g., lint the composed pipeline via GitLab's CI lint API or a `gitlab-ci-local` dry-run — so the sequence has a concrete feedback checkpoint (raises workflow_clarity).

Move the more composable advanced sections (matrix, `needs` DAG, `rules`) into a separate reference file such as `references/advanced.md`, linked one level deep from SKILL.md, so the body stays a lean overview (raises progressive_disclosure).

Include a short end-to-end "composing a full pipeline" example that assembles steps 1–9 and ends with a validate/run-and-check step, giving the multi-step process an explicit checkpoint.

DimensionReasoningScore

Conciseness

Nine tight YAML blocks each followed by one operational line (e.g., "Pin the key to package-lock.json so cache invalidates on dep changes") with no generic concept explanations, matching the lean score-3 anchor; the prose earns its place rather than padding.

3 / 3

Actionability

Each step ships a complete, executable `.gitlab-ci.yml` snippet (full `stages`/`script`/`artifacts`/`rules` blocks) that is copy-paste ready, satisfying the fully-executable score-3 anchor.

3 / 3

Workflow Clarity

Steps 1–9 form a clear progressive build-up and the Anti-patterns table acts as a checklist, but there is no explicit validation or verification checkpoint (e.g., lint the config or dry-run the pipeline), so it sits at the sequence-present-but-checkpoints-implicit level rather than 3.

2 / 3

Progressive Disclosure

Sectioning is clean (Overview, Steps 1–9, Anti-patterns, Limitations, References) but all content lives inline in a single ~245-line SKILL.md with no bundle files and nothing split one level deep into referenced material, so it is better than monolithic yet not the appropriately-split score-3 case.

2 / 3

Total

10

/

12

Passed

Description

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.

A strong, specific description that names concrete GitLab CI capabilities, includes an explicit "Use when" trigger, and is clearly distinguishable from sibling CI skills. Every dimension lands at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "parallel matrix, artifact reports (junit, coverage), services (postgres, redis), needs / dependencies between jobs, only/except + rules for trigger filtering, retry policy" — matching the score-3 anchor that expects several specific capabilities.

3 / 3

Completeness

Explicitly answers both what (the enumerated CI capabilities) and when via the "Use when the project hosts on GitLab and the team wants idiomatic GitLab CI patterns" trigger clause.

3 / 3

Trigger Term Quality

Uses natural terms a user would say — "GitLab CI/CD", ".gitlab-ci.yml", "GitLab CI patterns", "GitLab" — giving good coverage rather than abstract jargon.

3 / 3

Distinctiveness Conflict Risk

The "hosts on GitLab" trigger carves a clear GitLab CI niche distinct from the sibling GitHub Actions / Jenkins / CircleCI skills, so it is unlikely to fire for the wrong skill.

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.

Reviewed

Table of Contents