gitlab-automation
Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.
76
Quality
72%
Does it follow best practices?
Impact
76%
1.55xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/gitlab-automation/SKILL.mdDiscovery
67%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 effectively communicates specific GitLab automation capabilities with good domain coverage. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know exactly when to select this skill. The technical reference to 'Rube MCP (Composio)' adds implementation detail that doesn't help with skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about GitLab projects, creating MRs, checking pipeline status, or managing GitLab issues.'
Include common user variations and abbreviations like 'MR', 'CI/CD', 'GitLab CI', '.gitlab-ci.yml' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'project management, issues, merge requests, pipelines, branches, and user operations' - these are distinct, actionable GitLab features. | 3 / 3 |
Completeness | Clearly answers 'what' (automate GitLab operations) but lacks an explicit 'Use when...' clause. The 'when' is only implied by the domain terms, not explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes good domain terms like 'GitLab', 'issues', 'merge requests', 'pipelines', but missing common user variations like 'MR', 'CI/CD', 'repo', or file extensions. Technical term 'Rube MCP (Composio)' is jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | GitLab-specific focus with distinct triggers like 'merge requests' and 'pipelines' clearly distinguishes it from generic git skills or other project management tools like GitHub or Jira. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 well-structured, highly actionable skill for GitLab automation with clear workflows and comprehensive parameter documentation. The main weaknesses are some redundancy in pitfall documentation and the monolithic structure that could benefit from splitting into overview + reference files. The quick reference table and detailed tool sequences make this immediately usable.
Suggestions
Consolidate duplicate pitfall information - the per-workflow pitfalls and 'Known Pitfalls' section have significant overlap that could be merged
Consider splitting the detailed parameter lists and quick reference table into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with workflow sequences
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - pitfalls are repeated across sections and in a dedicated 'Known Pitfalls' section. The content is mostly efficient but could be tightened by consolidating duplicate information. | 2 / 3 |
Actionability | Provides concrete tool names, specific parameter names with exact values, and clear tool sequences for each workflow. The quick reference table and detailed parameter lists make this highly actionable and copy-paste ready. | 3 / 3 |
Workflow Clarity | Each workflow has numbered tool sequences with clear prerequisites, required vs optional steps, and explicit validation points (e.g., 'Verify project access', 'Confirm connection status shows ACTIVE'). The Setup section includes a clear verification flow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~300 lines) that could benefit from splitting detailed parameter references and pitfalls into separate files. The external toolkit docs link is good but internal structure could be improved. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.