jira-workflow-creator
Jira Workflow Creator - Auto-activating skill for Enterprise Workflows. Triggers on: jira workflow creator, jira workflow creator Part of the Enterprise Workflows skill category.
36
3%
Does it follow best practices?
Impact
99%
1.01xAverage 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-workflow-creator/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, essentially just a title with no substantive content. It fails to describe any concrete actions, lacks natural trigger terms users would say, and provides no guidance on when Claude should select this skill. The repeated trigger term 'jira workflow creator' adds no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Jira workflows with custom statuses, transitions, conditions, and validators. Configures workflow schemes and assigns them to projects.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating or configuring Jira workflows, workflow transitions, workflow schemes, status mappings, or Jira automation rules.'
Include common keyword variations users might say, such as 'jira workflow', 'workflow transitions', 'workflow steps', 'jira statuses', 'workflow scheme', '.jira', 'atlassian workflow'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Jira Workflow Creator') but does not describe any concrete actions. There are no specific capabilities listed such as creating workflows, defining transitions, configuring statuses, or setting up automation rules. | 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. The 'Triggers on' line is just a repeated skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'jira workflow creator' repeated twice. There are no natural user keywords like 'jira workflow', 'create workflow', 'workflow transitions', 'jira automation', 'workflow scheme', or other terms a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Jira' and 'Workflow Creator' provides some domain specificity that distinguishes it from generic skills, but the lack of detail about what specifically it does with Jira workflows means it could overlap with other Jira-related skills. | 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 meta-descriptions and trigger phrases without any actual instructions, code, configurations, or workflow steps for creating Jira workflows. It provides no value to Claude beyond what the skill's title already conveys.
Suggestions
Add concrete, executable examples of Jira workflow creation—e.g., REST API calls to create workflows, transition definitions in JSON/YAML, or Jira automation rule configurations.
Define a clear multi-step workflow: e.g., 1) Define statuses, 2) Define transitions, 3) Create workflow via API, 4) Validate workflow, 5) Assign to project scheme—with specific commands and validation checkpoints.
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content that teaches how to actually create and configure Jira workflows.
Add references to Jira REST API documentation or link to separate files for advanced patterns like post-functions, validators, conditions, and workflow schemes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. It explains trigger patterns and meta-information rather than providing any actual skill content. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no code, no commands, no specific steps, no configurations, no examples of Jira workflow definitions. The entire content describes what the skill supposedly does without actually doing or teaching anything. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. For a skill named 'Jira Workflow Creator,' there should be a clear multi-step process for creating workflows, but none is provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic boilerplate with no references to detailed materials, no links to examples, API docs, or configuration templates. There is no meaningful structure beyond placeholder 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.