gitlab-epic-creator
Gitlab Epic Creator - Auto-activating skill for Enterprise Workflows. Triggers on: gitlab epic creator, gitlab epic creator Part of the Enterprise Workflows skill category.
36
3%
Does it follow best practices?
Impact
98%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/gitlab-epic-creator/SKILL.mdQuality
Discovery
7%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 extremely weak, consisting essentially of a repeated title and a category label with no substantive content. It fails to describe what the skill does, when it should be used, or provide natural trigger terms that users would employ. It would be nearly indistinguishable from any other GitLab-related skill in a large skill library.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates GitLab epics with titles, descriptions, labels, milestones, and linked child issues from user requirements or project plans.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks to create a GitLab epic, plan a roadmap epic, organize issues into an epic, or set up epic-level tracking in GitLab.'
Include natural keyword variations users might say, such as 'epic', 'GitLab epic', 'create epic', 'new epic', 'roadmap planning', 'epic template', and '.gitlab' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Gitlab Epic Creator') but does not describe any concrete actions like creating epics, setting milestones, assigning labels, or linking issues. It is essentially a title repeated with no actionable detail. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a repeated trigger phrase with no meaningful guidance. There is no explicit 'Use when...' clause describing scenarios or user intents. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'gitlab epic creator' repeated twice. It misses natural user phrases like 'create an epic', 'GitLab epic', 'new epic', 'epic planning', or 'roadmap epic'. The terms are narrow and redundant. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Gitlab Epic' does narrow the domain somewhat, distinguishing it from generic project management or other GitLab skills. However, the lack of specificity about what it actually does (vs. other potential GitLab skills) still leaves room for overlap. | 2 / 3 |
Total | 5 / 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 instructional content. It repeatedly references 'gitlab epic creator' without ever explaining what a GitLab epic is in this context, how to use the GitLab API, or providing any actionable steps. Every section is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable examples showing GitLab API calls to create epics (e.g., using `curl` or Python with the `python-gitlab` library), including required fields and authentication.
Define a clear workflow: authenticate → create epic → add child issues → validate epic structure, with specific API endpoints and expected responses.
Include a real code example with the GitLab API endpoint (e.g., `POST /api/v4/groups/:id/epics`) and required payload fields like title, description, labels, and due dates.
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content that teaches Claude something it doesn't already know about GitLab epic creation patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'gitlab epic creator' excessively, and provides zero substantive information about how to actually create GitLab epics. | 1 / 3 |
Actionability | There are no concrete commands, API calls, code examples, or executable guidance whatsoever. The skill describes what it claims to do in vague terms ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. There is no sequence, no validation, no concrete process for creating GitLab epics. The content only lists abstract capabilities like 'validates outputs against common standards' without specifying how. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed materials, no links to API documentation, and no structured navigation to deeper content. The sections present are all superficial metadata rather than organized instructional 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
4dee593
- 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.