Tessl • The package manager for agent skills

Name: gitlab-ci-patterns
Rating: 50.4 (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

55%

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/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

57%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 a strong, actionable catalog of executable GitLab CI YAML patterns, but it is padded with generic boilerplate, lacks validation checkpoints in its deployment workflows, and points to bundle files that are not present.

Suggestions

Remove or replace the generic 'Instructions' and 'Best Practices' boilerplate with GitLab-specific guidance Claude would not already infer.

Add explicit validation checkpoints to deployment and Terraform apply workflows (e.g. 'kubectl rollout status' as a gate, 'terraform plan -detailed-exitcode' review before apply).

Either create the referenced bundle files (assets/gitlab-ci.yml.template, references/pipeline-stages.md, resources/implementation-playbook.md) or remove the dangling 'Reference Files' links to avoid broken navigation.

Dimension	Reasoning	Score
Conciseness	The bulk is lean YAML code, but generic boilerplate sections ('Clarify goals, constraints, and required inputs... Apply relevant best practices and validate outcomes') and a 10-item 'Best Practices' list of advice Claude already knows add padding that could be trimmed.	3 / 5
Actionability	Provides multiple copy-paste-ready YAML pipelines (basic, Docker build/push, multi-environment, Terraform, security scanning, caching, dynamic child pipelines) covering the common cases, with only minor placeholder gaps (example.com URLs, my-app names).	4 / 5
Workflow Clarity	The 'Instructions' sequence is generic with no concrete checkpoints, and the deployment/Terraform apply examples lack explicit validation gates; the rubric caps destructive/batch workflows without validation at 3.	3 / 5
Progressive Disclosure	Sections are clearly headed and a 'Reference Files' section signals external files, but the referenced paths (resources/implementation-playbook.md, assets/gitlab-ci.yml.template, references/pipeline-stages.md) do not exist, and large blocks of YAML that could live in templates are inlined.	3 / 5
	Total	13 / 20 Passed

Description

53%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 clearly identifies the GitLab CI/CD domain and lists standard pipeline actions, but leans on the vague buzzword 'Comprehensive' and omits any explicit 'Use when...' trigger guidance. It is competent but not exemplary.

Suggestions

Drop the empty modifier 'Comprehensive' and lead with concrete capabilities, e.g. 'Author GitLab CI/CD pipelines with stage organization, caching, Docker builds, and Kubernetes deployment.'

Append an explicit trigger clause: 'Use when creating or editing .gitlab-ci.yml files, configuring GitLab Runners, or setting up GitLab CI/CD pipelines.'

Add natural keyword variants users actually say (e.g. '.gitlab-ci.yml', 'GitLab Runner', 'GitOps') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('GitLab CI/CD pipeline patterns') and 2-3 concrete actions ('automated testing, building, and deployment'), but these are generic pipeline stages rather than distinctive capabilities, and the leading 'Comprehensive' is vague over-claim fluff.	3 / 5
Completeness	Provides a clear 'what' (pipeline patterns for testing/building/deployment) but no 'when' / 'Use when...' trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant natural terms ('GitLab CI/CD', 'pipeline', 'testing', 'building', 'deployment') but misses common variations users say such as '.gitlab-ci.yml', 'GitLab Runner', or 'GitLab pipeline config'.	3 / 5
Distinctiveness Conflict Risk	GitLab-specific phrasing gives it a clear niche with minimal conflict risk, though 'pipeline patterns for automated testing, building, and deployment' could overlap slightly with generic CI/CD or deployment-pipeline skills.	4 / 5
	Total	13 / 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/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.