gitlab-ci-basics
Gitlab Ci Basics - Auto-activating skill for DevOps Basics. Triggers on: gitlab ci basics, gitlab ci basics Part of the DevOps Basics skill category.
34
0%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/gitlab-ci-basics/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It fails on all dimensions: it describes no concrete actions, provides no natural trigger terms beyond the skill name repeated, lacks any 'Use when...' guidance, and is too generic to be distinguishable from other DevOps skills.
Suggestions
Add specific capabilities the skill covers, e.g., 'Explains GitLab CI/CD pipeline configuration, stages, jobs, runners, and .gitlab-ci.yml syntax.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about GitLab CI pipelines, .gitlab-ci.yml files, CI/CD configuration, GitLab runners, or pipeline stages.'
Diversify trigger terms to include common variations users would say: 'gitlab pipeline', 'CI/CD', '.gitlab-ci.yml', 'gitlab runner', 'gitlab jobs', 'gitlab stages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Gitlab Ci Basics') and references a category ('DevOps Basics') without describing what the skill actually does. | 1 / 3 |
Completeness | Neither the 'what does this do' nor the 'when should Claude use it' questions are meaningfully answered. There is no 'Use when...' clause and no description of capabilities. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'gitlab ci basics' repeated twice. There are no natural user keywords like 'pipeline', 'CI/CD', '.gitlab-ci.yml', 'runner', 'jobs', 'stages', or other terms users would naturally use. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'DevOps Basics' could overlap with many other skills related to CI/CD, Docker, Kubernetes, deployment, etc. There are no distinct triggers to differentiate it from other DevOps-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual GitLab CI content. It contains only generic boilerplate descriptions that could apply to any topic, provides zero actionable guidance, and wastes tokens on meta-descriptions rather than teaching Claude anything about GitLab CI pipelines, configuration, or best practices.
Suggestions
Add a concrete .gitlab-ci.yml example with common stages (build, test, deploy) that is copy-paste ready and demonstrates real pipeline configuration.
Include specific GitLab CI concepts like runners, artifacts, caching, and environment variables with executable configuration snippets.
Define a clear workflow for creating and validating a CI pipeline, e.g.: 1) Create .gitlab-ci.yml, 2) Validate with `gitlab-ci-lint` or the API, 3) Push and verify pipeline status.
Remove all generic filler text ('automated assistance', 'industry best practices') and replace with domain-specific, actionable content about GitLab CI.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler ('automated assistance', 'industry best practices', 'production-ready code') and explains nothing Claude doesn't already know. There is zero domain-specific information about GitLab CI. | 1 / 3 |
Actionability | There are no concrete commands, code examples, configuration snippets, or specific instructions. The entire skill is vague meta-description with no executable guidance whatsoever—no .gitlab-ci.yml example, no pipeline stages, no runner configuration. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is provided. There are no validation checkpoints or any indication of how to actually accomplish a GitLab CI task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed references, no bundle files, and no meaningful organization beyond boilerplate headings that contain no real content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.