Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

gitlab-ci-patterns

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

Quality

64%

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 ./skills/gitlab-ci-patterns/SKILL.md

Quality

Content

53%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's strength is a set of concrete, largely copy-paste-ready GitLab CI YAML patterns covering the main use cases. It is weakened by generic filler sections, no explicit workflow or validation guidance around destructive deployment operations, and a progressive-disclosure structure that inlines everything while referencing bundle files that do not exist.

Suggestions

Create the referenced bundle files (assets/gitlab-ci.yml.template, references/pipeline-stages.md, resources/implementation-playbook.md) or remove the dangling 'Reference Files' and 'Instructions' references, since none of them exist in the bundle.

Move the bulk of the YAML pattern catalog into a reference file and keep SKILL.md as a concise overview with well-signaled one-level-deep links, instead of inlining ~200 lines of examples.

Remove the filler 'Instructions', 'Purpose', and 'Do not use this skill when' sections, and add explicit validation gates for destructive operations (e.g., review the saved terraform plan before 'apply' rather than 'terraform apply -auto-approve').

Dimension	Reasoning	Score
Conciseness	The YAML examples themselves are lean, but the body carries unnecessary filler: the 'Instructions' section is generic boilerplate ('Clarify goals, constraints, and required inputs'), 'Purpose' restates the description, and 'Do not use this skill when' says only 'The task is unrelated to gitlab ci patterns'. The pinned 'TF_VERSION: "1.6.0"' is time-sensitive version information with no deprecated/old-patterns framing. Mostly efficient with sections that should be trimmed.	3 / 5
Actionability	The body provides eight complete, executable YAML configurations covering the common cases (basic pipeline, Docker build/push, multi-environment deploy, Terraform, security scanning, caching, dynamic child pipelines). Minor gaps keep it from a 5: the flagship 'deploy' job runs kubectl with no kubeconfig setup, and '$KUBE_URL'/'$KUBE_TOKEN' variables are assumed without definition.	4 / 5
Workflow Clarity	The skill is a pattern catalog with no narrated multi-step workflow and no explicit validation checkpoints; the 'Instructions' section is too vague to serve as one. Destructive operations appear without validation guidance ('terraform apply -auto-approve', production 'kubectl apply'), and the rubric caps workflow clarity at 3 for destructive/batch operations lacking validation steps.	3 / 5
Progressive Disclosure	Roughly 200 lines of pattern YAML are inlined in SKILL.md where a lean overview plus separate reference files would be appropriate, and the 'Reference Files' section points to 'resources/implementation-playbook.md', 'assets/gitlab-ci.yml.template', and 'references/pipeline-stages.md', none of which exist in the bundle (there are no references/, assets/, or resources/ directories). Broken navigation plus inlined bulk content matches the 'content that clearly belongs in separate files is inlined' anchor.	2 / 5
	Total	12 / 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 clearly identifies the GitLab CI/CD niche and reasonably natural trigger terms, but it entirely lacks a 'when to use' clause and describes capabilities only at a broad category level with buzzword padding ('Comprehensive'). It is serviceable but below the standard of the good examples.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or editing .gitlab-ci.yml files, configuring GitLab Runners, or setting up multi-stage build/test/deploy pipelines.'

Replace the buzzword 'Comprehensive' with 2-3 concrete capabilities, e.g. 'Set up multi-stage build/test/deploy pipelines, caching, Docker image publishing, and Terraform workflows.'

Include natural variations users would actually say, such as '.gitlab-ci.yml', 'GitLab Runner', and 'GitOps', to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('GitLab CI/CD pipeline patterns') and lists three broad activity areas ('automated testing, building, and deployment'), but these are generic category labels rather than concrete actions, and 'Comprehensive' is buzzword padding. It matches the anchor for naming a domain with only 1-2 non-comprehensive actions, not the level-above anchor requiring several specific actions.	3 / 5
Completeness	The 'what' is stated clearly, but there is no 'Use when...' clause or any equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3; it cannot reach 4 without at least a weak explicit 'when'.	3 / 5
Trigger Term Quality	Good coverage of the core natural phrases users would say: 'GitLab CI/CD', 'pipeline', 'deployment'. A few natural terms are missing, such as '.gitlab-ci.yml', 'GitLab Runner', and 'DevOps', so it falls between the 'some relevant keywords' (3) and 'comprehensive synonyms and extensions' (5) anchors, noticeably above the midpoint.	4 / 5
Distinctiveness Conflict Risk	'GitLab CI/CD' is a clear niche clearly distinguishable from adjacent CI/CD skills (e.g., GitHub Actions), giving minimal conflict risk. Minor overlap remains with generic CI/CD, deployment, and GitOps skills, which keeps it below the 'minimal conflict risk' anchor 5.	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: skills/gitlab-ci-patterns/SKILL.md
Revision: 64adc55

Reviewed: 14 days ago

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.

gitlab-ci-patterns

Table of Contents

Is this your skill?