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 content is well-structured and action-packed with executable commands, explicit validation checkpoints, and clear workflows. Its main weaknesses are a large inline Documentation Index that bloats token cost and references non-existent nested files, plus one incorrect script filename in the Execution Protocol.

Suggestions

Move the ~265-line Documentation Index out of SKILL.md into a dedicated generated file (e.g. references/docs-index.md) and link to it, or regenerate it so all listed paths actually exist under references/.

Fix the Execution Protocol step 1 command to reference the real filename: "uv run scripts/sync_gitlab_docs.py --working-dir ." (underscores, not dashes).

Resolve the references/ci/... links: either sync those files into the bundle or remove the dead Documentation Index section to prevent navigation to missing files.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and minimal concept padding, but the ~265-line inline Documentation Index (lines 359-625) is a large token-heavy block that could be tightened or moved to a separate generated file.

3 / 5

Actionability

Mostly executable, copy-paste-ready guidance (gitlab-ci-local, glab ci lint/status/get, validate_glfm.py invocations) with a minor gap: the Execution Protocol step 1 calls "scripts/sync-gitlab-docs.py" (dashes) while the actual file is "sync_gitlab_docs.py" (underscores), so that command is not runnable as written.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (Execution Protocol, Quick Start IF/then paths, glab COMMON WORKFLOW) with explicit validation checkpoints and checklists for CI config, GLFM, and local testing, plus feedback loops (validate before commit, test locally before pushing).

5 / 5

Progressive Disclosure

Core references are real and one-level-deep with clear signaling (Reference Documentation section, per-domain REFERENCES), but the Documentation Index inlines bulk content that should be a separate file and points to ~200 non-existent nested paths under references/ci/ (e.g. ci/runners/hosted_runners/linux.md), making that block unnavigable.

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 concise yet comprehensive: it states the domain, enumerates concrete capabilities, and provides an explicit "Use when..." trigger clause covering the skill's full scope. It is highly specific, distinct, and unlikely to fire for unrelated skills.

DimensionReasoningScore

Specificity

Names the domain and 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") with comprehensive coverage.

5 / 5

Completeness

Explicitly states both what ("GitLab CI/CD pipeline configuration and GLFM documentation expertise") and when ("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").

5 / 5

Trigger Term Quality

Includes natural, specific terms users would say plus file/tool identifiers (".gitlab-ci.yml", "gitlab-ci-local", "GitLab README/Wiki content", "Docker-in-Docker", "CI Steps"), giving comprehensive keyword coverage with extensions and synonyms.

5 / 5

Distinctiveness Conflict Risk

Targets a clear GitLab-only niche with distinct triggers (.gitlab-ci.yml, gitlab-ci-local, GitLab Wiki, CI Steps) that other skills would not match, giving minimal conflict risk.

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.