Tessl • The package manager for agent skills

gitlab-ci-patterns

Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.

1.42x

Quality

80%

Does it follow best practices?

Impact

97%

1.42x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/cicd-automation/skills/gitlab-ci-patterns/SKILL.md

The canonical home for this skill is gitlab-ci-patterns in wshobson/agents

Quality

Content

72%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.

A highly actionable, well-organized catalog of executable GitLab CI patterns with strong conciseness. Its main weaknesses are the absence of explicit validation feedback loops in deployment workflows and reference-file links that point to non-existent bundle files.

Suggestions

Add an explicit validation feedback loop to the deployment patterns (e.g., verify rollout, and if it fails, diagnose and re-apply) to lift workflow clarity above 3 for these destructive/batch operations.

Create the referenced `assets/gitlab-ci.yml.template` and `references/pipeline-stages.md` files, or remove the "Reference Files" section, so navigation links resolve to real bundle content.

Trim the Purpose and When-to-Use sections since they duplicate the frontmatter description, improving token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is code-first with terse headers and no over-explanation of concepts Claude already knows; minor redundancy comes from the Purpose and When-to-Use sections echoing the frontmatter description.	4 / 5
Actionability	It provides complete, copy-paste-ready YAML configs covering build/test/deploy, Docker push, multi-environment deploy, Terraform, security scanning, caching, and dynamic child pipelines across the common cases.	5 / 5
Workflow Clarity	The content is a pattern catalog rather than a sequenced Claude workflow; pipelines show stages and the deploy includes a manual gate plus `kubectl rollout status`, but there is no explicit validate->fix->retry feedback loop.	3 / 5
Progressive Disclosure	Sections are well-organized and inline code is appropriate for a patterns catalog, but the "Reference Files" section points to `assets/gitlab-ci.yml.template` and `references/pipeline-stages.md` that do not exist in the bundle, creating dead navigation links.	3 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong, third-person description that clearly states capabilities and provides explicit, concrete use-when triggers scoped to a distinct niche. Minor gains are possible by adding a few more natural trigger terms and broadening the capability list.

Dimension	Reasoning	Score
Specificity	"Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners" lists several concrete actions, but coverage is not comprehensive (e.g., no mention of security scanning or dynamic pipelines that the body actually covers).	4 / 5
Completeness	It explicitly answers both what ("Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners") and when ("Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like "implementing GitLab CI/CD", "optimizing pipeline performance", and "automated testing and deployment" give good keyword coverage, though a few common terms (".gitlab-ci.yml", "GitLab Runner") are missing.	4 / 5
Distinctiveness Conflict Risk	The GitLab CI/CD niche is clearly distinct from adjacent skills like GitHub Actions or Jenkins, with triggers scoped to GitLab-specific pipeline work and minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/cicd-automation/skills/gitlab-ci-patterns/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.