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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill gitlab-epic-creatorActivation
22%This description is severely underdeveloped, functioning more as a label than a useful skill description. It fails to explain what actions the skill performs (e.g., creating epics, setting milestones, assigning teams) and provides no meaningful guidance on when Claude should select it beyond the literal trigger phrase.
Suggestions
Add specific actions the skill performs, e.g., 'Creates GitLab epics with descriptions, labels, milestones, and child issues. Links related issues and sets due dates.'
Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user wants to create a GitLab epic, plan a feature initiative, or organize multiple issues under a parent epic.'
Add natural keyword variations users might say: 'epic', 'feature planning', 'issue hierarchy', 'gitlab project planning', 'parent issue'.
| 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 'what' is extremely weak (just a name) and there's no explicit 'when' guidance beyond listing trigger phrases. Missing a 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | Contains 'gitlab epic creator' as a trigger term (repeated twice), 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 Epic focus provides some distinctiveness, but 'Enterprise Workflows' is vague and could overlap with other enterprise-related skills. The specific 'gitlab epic' term helps but lacks detail. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only generic marketing-style descriptions without any concrete guidance on how to create GitLab epics, what API calls to make, what fields are required, or any executable examples. The skill fails on all dimensions by providing zero actionable content.
Suggestions
Add concrete, executable code examples showing GitLab API calls to create epics (e.g., POST /groups/:id/epics with required fields)
Define a clear workflow with specific steps: 1) Identify group ID, 2) Gather epic details, 3) Make API call, 4) Validate response
Include actual epic field specifications (title, description, labels, due dates) with example values
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with specific GitLab epic creation instructions
| 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 meaningless 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 processes documented for creating GitLab epics. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed documentation, no links to examples, and no structured navigation to additional resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.