CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/cicd-automation/skills/gitlab-ci-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The content is highly actionable with a broad library of executable GitLab CI patterns and minimal padding. Its weaknesses are structural and process-oriented: deployment/apply workflows lack explicit validation feedback loops, and the monolithic file ignores progressive disclosure despite clear opportunities to split patterns into references.

Suggestions

Add explicit validation checkpoints to destructive/batch workflows (e.g., after `terraform plan`, validate the plan before `apply`; after `kubectl apply`, verify rollout and define a fix-and-retry loop on failure) so workflow_clarity can exceed the cap of 3.

Move the larger pattern catalogs (e.g., Security Scanning, Dynamic Child Pipelines, Caching Strategies, Terraform) into separate reference files under `references/` and link to them from SKILL.md so the body stays a lean overview, improving progressive_disclosure.

Trim the prose "Best Practices" list into a concise checklist or fold each item into the relevant example, removing mild verbosity and lifting conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is mostly lean executable YAML with minimal explanatory padding and does not re-explain concepts Claude already knows; the small "Purpose", "When to Use", and prose-heavy "Best Practices" sections could be trimmed slightly, keeping it just below score 5.

4 / 5

Actionability

Multiple complete, copy-paste-ready YAML examples cover the common cases (basic pipeline, Docker build/push, multi-environment deploy, Terraform, security scanning, caching, dynamic child pipelines), matching the fully-executable score-5 anchor.

5 / 5

Workflow Clarity

Sequences are present and some manual gates / rollout-status checks appear, but destructive and batch operations (production deploy, terraform apply, docker push) lack explicit validate-then-fix-then-retry feedback loops; per the rubric this caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

The skill is well sectioned but is a 268-line monolithic SKILL.md with no bundle files or one-level-deep references; large pattern sets that would benefit from separate reference files are all inlined, matching the score-3 anchor.

3 / 5

Total

15

/

20

Passed

Description

83%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 strong: it states concrete capabilities and pairs them with an explicit, multi-clause "Use when" trigger. It is clearly distinct within the CI/CD skill family while remaining natural to invoke. Minor gains are available by adding a few more synonyms and tightening the broader triggers.

DimensionReasoningScore

Specificity

"Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners" names the domain plus several concrete capabilities; it falls short of score 5 only because the action list is not exhaustive.

4 / 5

Completeness

It explicitly answers both "what" (build pipelines with multi-stage workflows, caching, distributed runners) and "when" with concrete trigger phrases ("Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment"), matching the score-5 anchor.

5 / 5

Trigger Term Quality

The "Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment" clause covers several natural phrases users would say, missing only a few common synonyms such as "pipeline" alone or file extensions.

4 / 5

Distinctiveness Conflict Risk

"GitLab CI/CD" carves a clear niche distinct from sibling skills like github-actions-templates, but the broader triggers ("pipeline performance", "automated testing and deployment") leave minor overlap risk with adjacent CI/deployment skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.