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
Quality
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 severely lacking in substance. It essentially only provides a name and category without explaining what the skill does, what capabilities it offers, or when Claude should select it. The redundant trigger terms and absence of natural user language make it unlikely to be selected appropriately.
Suggestions
Add specific actions the skill performs, e.g., 'Creates and configures Jira workflows including transitions, conditions, validators, and post-functions'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to create Jira workflows, configure workflow transitions, set up approval processes, or automate Jira issue states'
Include varied trigger terms users would naturally say: 'jira workflow', 'workflow transitions', 'jira automation', 'issue workflow', 'approval workflow'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Jira Workflow Creator' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'creates workflows', 'configures transitions', or 'sets up automation rules'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('jira workflow creator' listed twice) and overly specific to the exact skill name. Missing natural variations users would say like 'create jira workflow', 'workflow automation', 'jira transitions', 'workflow rules', or 'jira process'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Jira' provides some specificity that distinguishes it from generic workflow tools, but 'workflow creator' is vague enough that it could conflict with other workflow-related skills. The category label 'Enterprise Workflows' doesn't help differentiate. | 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 essentially a placeholder with no substantive content. It describes what a Jira workflow creator skill should do but provides absolutely no actionable guidance, code examples, workflow steps, or concrete information about creating Jira workflows. The entire content could be replaced with actual instructions for configuring Jira workflows, API examples, or workflow definition schemas.
Suggestions
Add concrete, executable examples of Jira workflow configurations (e.g., JSON/YAML workflow definitions, REST API calls to create workflows)
Include step-by-step workflow creation process with specific Jira API endpoints and required parameters
Provide actual workflow patterns with code examples (e.g., approval workflows, status transitions, condition configurations)
Remove all generic boilerplate text and replace with specific, actionable guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual Jira workflow configurations. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow steps are provided whatsoever. Despite claiming to provide 'step-by-step guidance,' the skill contains no actual steps, sequences, or validation checkpoints for creating Jira workflows. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples or API documentation, and no organization beyond generic section headers. | 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
0c08951
- 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.