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. The Jira workflow transition focus provides good distinctiveness. 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 to done', 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—the core guidance (always query transitions first, IDs vary by instance) is buried in ~250 lines of implementation detail that could be split into reference files. The bulk transition workflow lacks validation checkpoints.
Suggestions
Reduce the main skill to ~50-80 lines covering the key insight (query transitions first), one concise code example, and the common mistakes section. Move TypeScript implementations and curl examples to separate reference files.
Add a verification step after bulk transitions (e.g., query issue status to confirm transition succeeded) to create a proper feedback loop for batch operations.
Split content into SKILL.md (overview + quick start + common mistakes) and referenced files like TRANSITIONS_API.md (curl examples), TYPESCRIPT_HELPERS.md (full implementation), and ERROR_REFERENCE.md.
Remove the type definitions and intermediate helper functions—Claude can infer these. Focus on the high-level moveIssueTo pattern and the critical 'always query first' constraint.
| 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 setting 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 (e.g., verify each transition succeeded before continuing, or confirm the issue is now in the expected state). This caps the score at 2 per the rubric's feedback loop requirement for batch operations. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with everything inline. The extensive TypeScript implementations, curl examples, error tables, and workflow discovery patterns should be split into separate reference files. There are no references to supplementary files except the jira-auth skill and the external API docs link. | 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
f772de4
- 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.