jira-transitions
Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting resolutions.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill jira-transitions81
Quality
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-transitions/SKILL.mdDiscovery
75%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 is a solid description that clearly defines its scope around Jira workflow transitions with an explicit 'Use when' clause. The main weaknesses are moderate specificity (could list more concrete transition actions) and limited trigger term coverage (missing common user phrasings like 'move ticket' or 'change status').
Suggestions
Add more natural trigger terms users might say, such as 'move ticket', 'change status', 'mark as done', 'close issue', 'reopen'
Expand the specific actions listed to include variations like 'bulk transitions', 'reopen closed issues', or 'move to backlog'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira workflow) and mentions specific actions (transitioning issues, setting resolutions) with example states, but doesn't list comprehensive concrete actions like 'move to backlog', 'reopen issues', or 'bulk transitions'. | 2 / 3 |
Completeness | Clearly answers both what (move Jira issues through workflow states) and when (transitioning issues or setting resolutions) with an explicit 'Use when' clause containing trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'Jira issues', 'To Do', 'In Progress', 'Done', 'transitioning', and 'resolutions', but missing common variations users might say like 'move ticket', 'change status', 'mark as done', 'close issue', or 'workflow'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Jira workflow transitions and resolutions; unlikely to conflict with general Jira skills (like creating issues or searching) due to the specific focus on state changes. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent workflow clarity and executable code examples. The main weakness is length - it could be more concise by removing redundant examples and splitting advanced content into separate files. The emphasis on querying transitions before executing them is a strong safety pattern.
Suggestions
Consider moving curl examples to a separate EXAMPLES.md file and keeping only one representative example inline
Remove the 'Common Transitions' table since it explicitly notes these vary by workflow - this adds tokens without reliable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy (e.g., the common transitions table with a note that names vary anyway, multiple similar curl examples). The TypeScript code is well-structured but could be more compact in places. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with proper type definitions, complete curl examples with actual request bodies, and specific API endpoints. Code is copy-paste ready with clear function signatures. | 3 / 3 |
Workflow Clarity | Excellent step-by-step progression from types to getting transitions to executing them. Explicitly emphasizes querying transitions first before attempting changes, includes validation in the high-level helper (checking if resolution is required), and bulk operations track success/failure. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~250 lines) and could benefit from splitting detailed curl examples or the bulk transition code into separate reference files. The single external reference to the API docs is appropriate. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.