Tessl • The package manager for agent skills

Name: gitlab-ci-patterns
Rating: 55.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

gitlab-ci-patterns

Comprehensive GitLab CI/CD pipeline patterns for automated testing, building, and deployment.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/gitlab-ci-patterns/SKILL.md

The canonical home for this skill is gitlab-ci-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

65%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 skill is highly actionable thanks to numerous executable YAML examples, but it is held back by generic boilerplate instructions, no real validation-focused workflow guidance for destructive deploys, and broken references to bundle files that are not present. Tightening the prose and either creating or removing the referenced files would lift the weaker dimensions.

Suggestions

Delete the generic 'Instructions' and tautological 'Do not use this skill when' bullets, or replace them with GitLab-CI-specific workflow steps with explicit validation checkpoints (e.g. lint .gitlab-ci.yml, run terraform validate before plan, verify rollout before marking success).

Resolve the dangling references: either ship assets/gitlab-ci.yml.template, references/pipeline-stages.md, and resources/implementation-playbook.md, or remove the 'Reference Files' line and the playbook pointer.

Move the bulk pattern catalog into a reference file and keep SKILL.md as a concise overview with one-level-deep, clearly signaled links to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The YAML examples are lean and assume Claude's competence, but the generic 'Instructions' ('Clarify goals...', 'Apply relevant best practices...'), tautological 'Do not use this skill when' bullets, and a repeated opening line are padding that applies to any skill.	3 / 5
Actionability	The body provides multiple complete, copy-paste-ready YAML pipelines (basic build/test/deploy, Docker build+push, multi-env kubectl, Terraform validate/plan/apply, security scanning, caching, child pipelines) covering the common GitLab CI cases.	5 / 5
Workflow Clarity	Individual examples show sequenced stages and some verification (terraform validate/plan, kubectl rollout status), but the top-level 'Instructions' workflow is generic boilerplate with no validation checkpoints for destructive deploy/apply operations.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but the body inlines a large pattern catalog that could live in reference files, and the cited bundles (assets/gitlab-ci.yml.template, references/pipeline-stages.md, resources/implementation-playbook.md) do not exist, leaving dangling references.	3 / 5
	Total	14 / 20 Passed

Description

61%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 third-person, on-domain, and reasonably distinctive, but it lacks any explicit trigger/usage guidance and leans on generic CI/CD stage names plus a 'Comprehensive' buzzword. Adding a 'Use when...' clause with file/keyword triggers would materially raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building or editing .gitlab-ci.yml files, configuring GitLab Runners, or designing GitLab CI/CD pipelines.'

Replace the generic stage list with concrete capabilities (e.g. 'multi-stage builds, Docker-in-Docker image pushes, kubectl/Terraform deploys, caching, and security scanning') to improve specificity.

Drop the filler word 'Comprehensive' and add natural synonyms like '.gitlab-ci.yml' and 'GitLab Runner' for better trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the GitLab CI/CD domain and three actions ('automated testing, building, and deployment'), but those are generic pipeline stages rather than concrete, comprehensive capabilities; the word 'Comprehensive' is filler.	3 / 5
Completeness	It gives a clear 'what' (CI/CD pipeline patterns for testing/building/deployment) but includes no 'Use when...' clause, so per the judging guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	'GitLab CI/CD' and 'pipeline' are natural terms a user would say, but common synonyms and file triggers like '.gitlab-ci.yml' or 'GitLab Runner' are missing.	4 / 5
Distinctiveness Conflict Risk	'GitLab CI/CD pipeline patterns' carves out a clear niche distinct from GitHub Actions or generic pipeline design, with only minor overlap risk against closely related deployment skills.	4 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/gitlab-ci-patterns/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.