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 essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no meaningful trigger terms beyond repeating its own name, and lacks any 'Use when...' guidance. It would be nearly useless for Claude to differentiate this skill from others in a large skill library.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates Jira tickets with populated summary, description, priority, and story points from user requirements or bug reports.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks to create a Jira ticket, file a bug, write a user story, or log an issue in Jira.'
Include natural keyword variations users would say, such as 'Jira issue', 'bug ticket', 'user story', 'sprint backlog item', 'JIRA task', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Jira Ticket Generator') but does not describe any concrete actions like creating tickets, populating fields, setting priorities, or formatting descriptions. It only states a category label. | 1 / 3 |
Completeness | The 'what' is extremely weak (just a name, no actions described) and the 'when' is essentially absent—there is no explicit 'Use when...' clause or meaningful trigger guidance beyond repeating the skill name. | 1 / 3 |
Trigger Term Quality | The 'Triggers on' field redundantly lists 'jira ticket generator' twice. It lacks natural user terms like 'create a Jira ticket', 'Jira issue', 'bug report', 'story', 'task', or 'backlog item' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Jira' provides some domain specificity that distinguishes it from generic document or code skills, but the lack of concrete actions or scope means it could overlap with any Jira-related skill. | 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 shell with no substantive content. It consists entirely of generic boilerplate that describes what the skill would do without providing any actual instructions, code, templates, or workflows for generating Jira tickets. It fails on every dimension because it contains zero actionable information.
Suggestions
Add concrete Jira ticket templates with example fields (summary, description, acceptance criteria, story points) and show exact JSON payloads for the Jira REST API.
Include a clear workflow: gather requirements → select issue type → populate fields → validate required fields → create ticket via API, with validation at each step.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace with actual executable guidance such as API endpoints, field mappings, and example ticket structures.
Add examples showing different ticket types (bug, story, epic, task) with concrete input/output pairs demonstrating the expected format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'jira ticket generator' excessively, and provides zero actual information about how to generate Jira tickets. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, commands, API calls, or any executable guidance whatsoever. The skill describes what it does in abstract terms without ever showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or processes described. | 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 structured navigation to deeper 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
dc559db
- 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.