jira-ticket-generator
Jira Ticket Generator - Auto-activating skill for Enterprise Workflows. Triggers on: jira ticket generator, jira ticket generator Part of the Enterprise Workflows skill category.
36
3%
Does it follow best practices?
Impact
97%
1.05xAverage 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/jira-ticket-generator/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—it reads more like a metadata label than a functional description. It provides no concrete actions, no natural trigger terms beyond the skill name repeated, and no guidance on when Claude should select this skill. The only redeeming quality is that 'Jira' provides a small degree of domain specificity.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates Jira tickets with structured titles, descriptions, acceptance criteria, and priority fields from user requirements or bug reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Jira ticket, write a Jira issue, draft a bug report for Jira, or generate a story/task/epic.'
Remove the duplicated trigger term ('jira ticket generator' listed twice) and replace with diverse natural language variations users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Jira Ticket Generator') but provides no concrete actions. It doesn't describe what the skill actually does—no mention of creating tickets, populating fields, formatting descriptions, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'jira ticket generator' repeated twice. There are no natural variations users might say like 'create a Jira issue', 'write a ticket', 'bug report', 'story', 'task', or 'JIRA'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Jira' provides some specificity that distinguishes it from generic ticket or document skills, but the lack of detail about what it does versus other potential Jira-related skills (e.g., Jira search, Jira status updates) creates overlap risk. | 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 placeholder with no actionable content whatsoever. It repeatedly references 'jira ticket generator' without providing any concrete guidance, code, templates, field definitions, or workflows. It fails on every dimension of the rubric.
Suggestions
Add a concrete Jira ticket template with actual fields (summary, description, acceptance criteria, story points, labels, etc.) and example values that Claude can use to generate tickets.
Include a step-by-step workflow for gathering requirements from the user and mapping them to Jira ticket fields, with validation checkpoints (e.g., confirm ticket type, verify acceptance criteria are testable).
Provide at least 2-3 complete input/output examples showing a user request and the resulting well-formed Jira ticket.
Remove all the generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace them with actionable content—field schemas, formatting rules, and best practices specific to Jira ticket creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, repeating 'jira ticket generator' excessively. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no code, no commands, no templates, no examples of actual Jira ticket formats or fields. The content only describes what the skill could do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. The skill claims to provide 'step-by-step guidance' but contains no steps, no sequence, and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples or templates, and no meaningful structural organization beyond boilerplate headings. | 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.