gitlab
Create and manage GitLab issues, merge requests, pipelines, and repositories using the glab CLI. Use when asked to open an MR, review a merge request, check CI/CD pipelines, list issues, or manage code review on GitLab.
92
Does it follow best practices?
Evaluation — 84%
↑ 1.52xAgent success when using this skill
Validation for skill structure
Discovery
100%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 is an excellent skill description that follows best practices. It uses third person voice, lists specific capabilities, includes a clear 'Use when...' clause with natural trigger terms, and is distinctly positioned for GitLab workflows. The inclusion of both 'MR' and 'merge request' shows good coverage of user vocabulary.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create and manage GitLab issues, merge requests, pipelines, and repositories using the glab CLI.' This covers four distinct capabilities with the specific tool mentioned. | 3 / 3 |
Completeness | Clearly answers both what ('Create and manage GitLab issues, merge requests, pipelines, and repositories') AND when ('Use when asked to open an MR, review a merge request, check CI/CD pipelines, list issues, or manage code review on GitLab'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'MR', 'merge request', 'CI/CD pipelines', 'issues', 'code review', 'GitLab'. Covers both abbreviations (MR) and full terms (merge request). | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishable with GitLab-specific terminology (glab CLI, MR, GitLab). Would not conflict with GitHub skills due to explicit GitLab references and the glab tool mention. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. The verification steps in examples demonstrate good practice for operations that need confirmation. The main weakness is some verbosity in listing commands that could be consolidated or deferred to official documentation references.
Suggestions
Consider consolidating the command reference sections - the detailed glab command listings duplicate information available in the linked official documentation and could be reduced to just the most common operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - command references are listed both in the script usage section and the direct glab usage section. The extensive command listings could be trimmed since Claude can reference official docs. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout. Examples are concrete with specific flags and arguments, and the distinction between wrapper script usage and direct glab commands is clear. | 3 / 3 |
Workflow Clarity | Multi-step workflows include explicit verification steps (e.g., 'Verify approval was recorded', 'Verify MR was created and linked', 'Verify pipeline restarted'). The examples section demonstrates clear sequences with validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from prerequisites to basic usage to advanced features. References external docs appropriately (common-workflows.md, official documentation links) without deep nesting. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.