jira-transitions
Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting resolutions.
71
63%
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. It is concise, uses third person voice, and targets a specific niche within Jira operations. The main weakness is that trigger terms could be expanded to cover 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
42%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 complete, executable code examples and good coverage of edge cases (resolution requirements, error handling). However, it is far too verbose for a skill file—much of the content (full type definitions, multiple curl variants, workflow discovery) could be condensed or split into referenced files. The bulk transition workflow lacks explicit validation checkpoints.
Suggestions
Reduce the content by 60-70%: remove full TypeScript type definitions (Claude can infer these), consolidate curl examples to one annotated example, and move the workflow discovery pattern to a separate reference file.
Split detailed content into referenced files: e.g., TRANSITIONS-API.md for curl examples and error codes, BULK-OPERATIONS.md for bulk transition patterns with proper validation.
Add explicit validation to the bulk transition workflow: include a dry-run step, progress reporting, and a checkpoint to review failures before continuing.
Condense the 'Common Mistakes' and 'Important Notes' sections into a single concise warnings block at the top, since they overlap (both warn about querying transition IDs first).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250 lines. It includes full TypeScript type definitions, multiple helper functions, and extensive curl examples that could be significantly condensed. Claude doesn't need step-by-step scaffolding for building a Jira transition wrapper—the key insight (always query transitions first, IDs vary) could be conveyed in a fraction of the space. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript code and complete curl examples with proper headers, request bodies, and response handling. Code is copy-paste ready with concrete examples for all common scenarios including resolution handling and comments. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (query transitions → find by name → execute), and the critical warning about querying first is prominent. However, for bulk transitions—a destructive batch operation—there's no explicit validation checkpoint or feedback loop (e.g., verify each transition succeeded before continuing, or dry-run mode). This caps the score at 2 per the rubric's feedback loop guidance. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to separate files. The type definitions, curl examples, error handling tables, and workflow discovery pattern could all be split into referenced files. Everything is inline in one massive document with no layered navigation. | 1 / 3 |
Total | 7 / 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
e437c3c
- 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.