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.
41
Quality
11%
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
22%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 severely underdeveloped, essentially serving as a label rather than a functional skill description. It lacks any explanation of what creating a GitLab epic entails, what specific actions the skill performs, and provides no meaningful guidance for when Claude should select it over other skills.
Suggestions
Add specific actions the skill performs, e.g., 'Creates GitLab epics with titles, descriptions, labels, and milestones. Links child issues and sets due dates.'
Include a 'Use when...' clause with natural trigger terms like 'create epic', 'new gitlab epic', 'epic planning', 'organize issues into epic'
Remove the duplicate trigger term and expand coverage to include variations users would naturally say when needing this functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Gitlab Epic Creator') but provides no concrete actions. It doesn't explain what creating an epic involves or what specific capabilities are offered. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and while it mentions triggers, there's no explicit 'Use when...' clause explaining when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains 'gitlab epic creator' as a trigger term (duplicated), which is somewhat relevant but misses natural variations users might say like 'create epic', 'new epic', 'gitlab issue', or 'epic planning'. | 2 / 3 |
Distinctiveness Conflict Risk | The GitLab-specific focus provides some distinctiveness, but 'Enterprise Workflows' is vague and could overlap with other enterprise tools. The lack of specific actions makes it harder to distinguish from other GitLab-related skills. | 2 / 3 |
Total | 6 / 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 content is essentially a placeholder template with no actual instructional value. It contains only generic descriptions of what a skill should do without any concrete guidance on GitLab epic creation - no API calls, no CLI commands, no field specifications, no examples of epic structures or workflows.
Suggestions
Add concrete, executable examples showing how to create GitLab epics via API or CLI (e.g., `curl` commands or Python code using python-gitlab)
Include a clear workflow with specific steps: define epic fields, set parent/child relationships, configure labels, assign to milestones, with validation checkpoints
Provide example epic structures showing required vs optional fields, proper formatting for descriptions, and linking to issues
Remove all generic boilerplate text and replace with actionable content specific to GitLab epic creation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual epic creation. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for creating GitLab epics. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 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
0c08951
- 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.