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

82%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 content is a tight, executable GitLab CI reference with copy-paste YAML for every step and a useful anti-patterns table. It loses a little on conciseness for minor restating and on workflow/progressive disclosure for the absence of an explicit validation checkpoint and any advanced-pattern reference.

Suggestions

Add a brief verification step (e.g., lint with `gitlab-ci-local` or check the pipeline UI) so destructive/misconfigured pipelines are caught before merge.

Trim the Overview's stages→jobs→steps definition and restating notes like '`parallel: matrix:` runs the job once per matrix entry' to assume Claude's familiarity.

Add a one-level-deep reference (e.g., references/include-splitting.md) for large-pipeline `include:` patterns mentioned only in Limitations.

DimensionReasoningScore

Conciseness

The body is mostly lean — code-first with brief GitLab-specific notes — but the Overview's stages→jobs→steps explanation and a few restating notes ('runs the job once per matrix entry') could be trimmed; assumes Claude's competence on most general concepts.

4 / 5

Actionability

Each step provides complete, copy-paste-ready `.gitlab-ci.yml` snippets covering the common cases (basic job, matrix, services, artifacts, needs, retry, rules, cache, variables), with concrete field values rather than pseudocode.

5 / 5

Workflow Clarity

Steps are clearly sequenced as an incremental build-up (basic → matrix → services → reports → DAG → retry → rules → cache → variables) with an Anti-patterns table acting as guardrails, though there is no explicit 'validate your .gitlab-ci.yml' checkpoint.

4 / 5

Progressive Disclosure

Well-organized single-file structure with per-step sections, Anti-patterns, Limitations, and References; no bundle files are needed for a CI cheat-sheet, though no deeper reference exists for advanced patterns like `include:` splitting of large pipelines.

4 / 5

Total

17

/

20

Passed

Description

100%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 specific, trigger-rich, and explicitly covers both capability and usage conditions, clearly scoping the skill to GitLab CI/CD. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — parallel matrix, artifact reports (junit, coverage), services (postgres, redis), needs/dependencies, only/except + rules, retry policy — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (configures GitLab CI/CD test stages with the listed features) and 'when' ('Use when the project hosts on GitLab and the team wants idiomatic GitLab CI patterns') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural terms users would say — 'GitLab CI/CD', 'test stages', the `.gitlab-ci.yml` file extension, 'hosts on GitLab' — plus synonyms and the config filename.

5 / 5

Distinctiveness Conflict Risk

Clear GitLab CI/CD niche with the 'hosts on GitLab' trigger and `.gitlab-ci.yml` filename, distinguishing it from sibling GitHub Actions / Jenkinsfile skills with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents