jira-transitions
Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting resolutions.
76
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-transitions/SKILL.mdQuality
Discovery
85%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, well-structured skill description that clearly communicates both what the skill does and when to use it. The explicit 'Use when...' clause with concrete workflow states provides good trigger guidance. The main weakness is that trigger term coverage could be broader to capture more natural user phrasings like 'change status', 'close ticket', or 'mark as done'.
Suggestions
Expand trigger terms to include common user phrasings like 'change status', 'close ticket', 'mark as done', 'move ticket', or 'update issue status'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: moving issues through workflow states, transitioning issues between named states (To Do, In Progress, Done), and setting resolutions. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Move Jira issues through workflow states') and when ('Use when transitioning issues (To Do, In Progress, Done) or setting resolutions') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good terms like 'Jira issues', 'transitioning', 'To Do', 'In Progress', 'Done', and 'resolutions', but misses common user variations like 'move ticket', 'change status', 'close issue', 'workflow transition', or 'mark as done'. | 2 / 3 |
Distinctiveness Conflict Risk | Narrowly scoped to Jira workflow transitions and resolutions specifically, which is a clear niche distinct from general Jira operations like creating issues, searching, or commenting. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with executable code and clear workflow sequencing, but it is far too verbose for a SKILL.md file. It dumps everything—type definitions, multiple helper functions, curl examples, tables, and error handling—into a single monolithic document, violating both conciseness and progressive disclosure principles. The core insight (transition IDs vary, always query first) could be conveyed in a fraction of the space.
Suggestions
Reduce the SKILL.md to a concise overview (~50-80 lines) covering the key pattern (query transitions first, then execute) with one TypeScript example and one curl example, moving detailed implementations to separate reference files.
Extract the full TypeScript implementation (types, helpers, bulk operations, workflow discovery) into a separate file like IMPLEMENTATION.md or a code file, and reference it from the main skill.
Remove the Common Transitions table or reduce it to a single-line note, since the skill already emphasizes that transition names vary by instance—the table adds little value and may mislead.
Consolidate the curl examples to just one (transition with resolution) since the others are trivially derivable, and Claude already knows how to construct curl requests.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose at ~250 lines. It includes full TypeScript type definitions, multiple helper functions, curl examples, AND tables that largely duplicate each other. Claude already knows how to structure TypeScript interfaces and make REST calls. The common transitions table even admits the names vary, making it low-value. Much of this could be condensed to the key pattern (always query transitions first) plus one code example and one curl example. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript code and complete curl commands with proper headers, request bodies, and endpoint paths. The code is copy-paste ready with concrete examples including transition IDs, issue keys, and JSON payloads. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced (define types → get transitions → find by name → execute → bulk). The critical validation point ('always query available transitions first') is prominently called out, the high-level helper checks for required resolution fields, and the bulk transition function tracks success/failure. Error handling with specific HTTP codes and solutions is well-documented. | 3 / 3 |
Progressive Disclosure | All content is inlined in a single monolithic file with no references to supporting files (except a link to jira-auth skill and the Atlassian API docs). The TypeScript implementations, curl examples, error handling tables, and workflow discovery patterns could all be split into separate reference files. The skill would benefit greatly from a concise overview with pointers to detailed materials. | 1 / 3 |
Total | 8 / 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.
- Repository
- NeverSight/skills_feed
- Commit
aa009ea
- 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.