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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill jira-ticket-generatorActivation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The repeated trigger term and boilerplate category mention provide no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Jira tickets with structured fields including summary, description, priority, and story points from natural language requests'
Include a proper 'Use when...' clause with natural trigger terms like 'create jira ticket', 'new issue', 'log a bug', 'create story', 'add task to jira'
Remove the redundant repeated trigger term and replace with diverse variations users would naturally say
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Jira Ticket Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating tickets, formatting, fields, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. Both components are essentially missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'jira ticket generator' repeated twice. This is redundant and misses natural variations users would say like 'create jira ticket', 'new issue', 'bug report', 'story', or 'task'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Jira' provides some specificity that distinguishes it from generic ticket/issue skills, but 'Enterprise Workflows' is vague and the lack of detail about what kind of Jira operations it handles could cause overlap with other Jira-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content about Jira ticket generation. It contains only generic boilerplate text that could apply to any skill, with no specific guidance, examples, templates, or workflows for creating Jira tickets. The skill provides zero value in its current form.
Suggestions
Add concrete Jira ticket templates with example JSON/YAML showing required fields (summary, description, issue type, priority, labels, components)
Include a workflow for ticket creation: gather requirements -> select issue type -> fill template -> validate required fields -> format output
Provide 2-3 complete example tickets showing different issue types (bug, story, task) with realistic content
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific Jira ticket formatting rules and conventions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Jira ticket generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, templates, or examples of actual Jira ticket formats. The content describes what the skill does abstractly but provides zero executable guidance on how to generate Jira tickets. | 1 / 3 |
Workflow Clarity | No workflow steps are provided. There's no sequence for creating tickets, no validation checkpoints, and no actual process to follow. The 'Capabilities' section lists vague promises without any implementation. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples file, no template references, and no links to Jira API documentation or ticket schemas. | 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.