CtrlK
BlogDocsLog inGet started
Tessl Logo

gitlab-skill

GitLab CI/CD pipeline configuration and GLFM documentation expertise. Use when modifying .gitlab-ci.yml, optimizing pipelines, testing with gitlab-ci-local, writing GitLab README/Wiki content, configuring Docker-in-Docker workflows, or implementing CI Steps composition.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable with strong, validated workflows and mostly real, well-organized references, but it is undermined by structural redundancy (reference links repeated four ways) and a large inline Documentation Index whose ~159 links point to non-existent files. Fixing the dead index and deduplicating the reference listings would lift both conciseness and progressive disclosure.

Suggestions

Remove or relocate the 265-line Documentation Index: its ~159 links target references/ci/** which does not exist, so it is dead navigation and should be generated into a separate reference file (or dropped) rather than inlined in SKILL.md.

Deduplicate reference listings: keep links in their per-domain REFERENCES sections and remove the redundant 'Reference Documentation' and 'Quick Start Paths' re-listings, or consolidate into a single canonical index.

Correct the Execution Protocol's first command from 'scripts/sync-gitlab-docs.py' to the actual filename 'scripts/sync_gitlab_docs.py' so the primary activation step is executable.

DimensionReasoningScore

Conciseness

Core domain guidance is efficient, but reference links are repeated across four locations (per-domain REFERENCES, the Reference Documentation section, Quick Start Paths, and the 265-line inline Documentation Index), and the 'The model must apply for ...' boilerplate recurs mechanically — noticeably redundant sections that could be tightened.

3 / 5

Actionability

Mostly copy-paste ready commands (gitlab-ci-local, glab ci lint/status/get with exact flags, uv run validate_glfm.py), but the Execution Protocol's first activation step references scripts/sync-gitlab-docs.py while the actual bundle file is sync_gitlab_docs.py, so that primary command would fail as written.

4 / 5

Workflow Clarity

Clear sequenced workflows (Execution Protocol, Quick Start Paths, setup procedures) with explicit validation checkpoints — three detailed validation checklists plus validate_glfm.py/gitlab-ci-local/glab ci lint feedback loops — meeting the anchor for explicit validation steps and checklists.

5 / 5

Progressive Disclosure

The eight domain-referenced files exist and are well-signaled one level deep, but the inline Documentation Index is a 265-line blob whose ~159 links all point to a references/ci/ tree that does not exist — content that belongs in a separate file is inlined and the navigation hub is largely dead.

3 / 5

Total

15

/

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 exemplary: it concisely states the skill's purpose and provides concrete, natural trigger conditions with file extensions and tool names that distinguish it from generic CI/CD skills. Both the 'what' and 'when' are explicitly answered in third person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'modifying .gitlab-ci.yml, optimizing pipelines, testing with gitlab-ci-local, writing GitLab README/Wiki content, configuring Docker-in-Docker workflows, ... implementing CI Steps composition' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly states what ('GitLab CI/CD pipeline configuration and GLFM documentation expertise') and when ('Use when modifying .gitlab-ci.yml, optimizing pipelines, ...'), with concrete trigger phrases mirroring the top good example.

5 / 5

Trigger Term Quality

Combines natural user phrases with concrete file extensions and tool names ('modifying .gitlab-ci.yml', 'gitlab-ci-local', 'Docker-in-Docker', 'GitLab README/Wiki'), matching the anchor for comprehensive keyword coverage including synonyms and extensions.

5 / 5

Distinctiveness Conflict Risk

GitLab-specific file extensions and tool names (.gitlab-ci.yml, gitlab-ci-local, GLFM, Docker-in-Docker, CI Steps) carve a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (626 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 159 missing, 164 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
Jamie-BitFlight/claude_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.