CtrlK
BlogDocsLog inGet started
Tessl Logo

odyssey4me/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.

72

Quality

90%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with clear workflows and good verification steps. Its main weakness is verbosity — the extensive inline command reference tables for direct glab usage could be offloaded to a reference file, and some sections (Configuration, Aliases, Troubleshooting) add marginal value for an AI agent that can consult official docs. The distinction between wrapper script (read) and direct glab (write) is well-communicated.

Suggestions

Move the direct glab command listings (Issues, MRs, Pipelines, Repos, Releases sections) into a separate reference file to reduce the main SKILL.md size and improve progressive disclosure.

Remove or significantly trim the Configuration, Aliases, and Troubleshooting sections — these are standard CLI concerns Claude can handle without explicit instruction.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary sections like Configuration, Aliases, and Troubleshooting that Claude already knows or can look up. The direct glab command listings largely duplicate official docs without adding unique value. The Model Guidance section is a single line that adds little.

2 / 3

Actionability

Commands are concrete, copy-paste ready, and cover both the wrapper script and direct glab usage. Examples include specific flags, arguments, and real command patterns. The distinction between read (script) and write (direct glab) operations is clearly actionable.

3 / 3

Workflow Clarity

The Examples section provides clear multi-step workflows (Daily MR Review, Create Issue and Link MR, Monitor CI Pipeline) with explicit verification steps after actions (e.g., 'Verify approval was recorded', 'Verify MR was created and linked', 'Verify pipeline restarted'). These feedback loops are appropriate for the operations involved.

3 / 3

Progressive Disclosure

References to permissions.md and common-workflows.md are well-signaled and one level deep, which is good. However, the main SKILL.md is quite long with extensive inline command references that could be split into a separate reference file. The bulk of the direct glab commands section is essentially a reference card that inflates the main file.

2 / 3

Total

10

/

12

Passed

Description

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 a strong skill description that clearly identifies the tool (glab CLI), the platform (GitLab), specific capabilities (issues, merge requests, pipelines, repositories), and explicit trigger conditions. It uses third person voice correctly and includes natural user terms like 'MR', 'merge request', 'CI/CD pipelines', and 'code review'. The description is concise yet comprehensive, making it easy for Claude to select appropriately.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: create and manage issues, merge requests, pipelines, and repositories. The description names the specific tool (glab CLI) and covers several distinct operations.

3 / 3

Completeness

Clearly answers both 'what' (create and manage GitLab issues, MRs, pipelines, repos using glab CLI) and 'when' (explicit 'Use when...' clause with specific trigger scenarios like opening MRs, checking pipelines, listing issues).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms 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 scoped to GitLab specifically and the glab CLI tool, which distinguishes it from GitHub-related skills or generic git skills. The GitLab-specific terminology (merge requests vs pull requests, glab vs gh) creates a distinct niche.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents