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.
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-workflow-creatorActivation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It lacks any explanation of capabilities, concrete actions, or guidance on when to use it. The redundant trigger terms and absence of natural user language make it unlikely to be selected appropriately from a skill library.
Suggestions
Add specific actions the skill performs, e.g., 'Creates and configures Jira workflows including transitions, conditions, validators, and post-functions'
Include 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'
Add varied trigger terms users would naturally say: 'jira workflow', 'workflow transitions', 'jira automation', 'issue workflow', 'approval workflow', 'jira process'
| 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, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Only provides category metadata without functional information. | 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 'Jira Workflow' specificity provides some distinction from generic workflow tools, but without describing actual capabilities, it could conflict with other Jira-related skills or general workflow automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template with no actionable information about Jira workflow creation. It consists entirely of generic boilerplate that could apply to any skill topic, providing zero specific guidance, code examples, or workflow steps for the stated purpose.
Suggestions
Add concrete examples of Jira workflow configurations (e.g., YAML/JSON for workflow schemes, transition rules, or API calls to create workflows)
Include step-by-step instructions for common workflow creation tasks with specific Jira API endpoints or UI navigation paths
Provide executable code snippets for workflow automation using Jira REST API or Atlassian SDK
Remove generic capability descriptions and replace with actual workflow patterns, validation steps, and error handling guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Jira workflow creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, API calls, or specific instructions for creating Jira workflows. The content describes what the skill does abstractly rather than providing executable guidance. | 1 / 3 |
Workflow Clarity | No actual workflow steps are provided. The 'step-by-step guidance' mentioned in capabilities is never delivered - there are no sequences, validation checkpoints, or process flows. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no navigation to deeper resources or structured content organization. | 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.