Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows. Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management.
97
Does it follow best practices?
Evaluation — 100%
↑ 2.43xAgent success when using this skill
Validation for skill structure
Discovery
100%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 an excellent skill description that follows best practices. It uses third person voice, lists specific capabilities, includes an explicit 'Use when...' clause with natural trigger terms, and is clearly distinguishable from other skills through Jira-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (search/manage issues, create/update tickets, manage workflows) AND when (explicit 'Use when...' clause with multiple trigger scenarios like finding tickets, checking backlog, managing sprints). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Jira tickets', 'backlog', 'sprints', 'bugs', 'Atlassian project management', 'JQL queries'. These match how users naturally discuss project management tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Jira-specific terminology (JQL, Atlassian, sprints, backlog). Unlikely to conflict with generic document or code skills due to clear project management and Jira focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. The main weakness is moderate verbosity - some sections could be tightened without losing clarity, particularly the setup verification explanations and repeated argument documentation patterns.
Suggestions
Condense the 'This validates/checks' lists into inline comments or remove them entirely since the check command output will show this information
Consider consolidating repeated argument documentation patterns into a single reference section rather than repeating for each command
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as explaining what each check validates and repeating similar patterns across commands. The installation and setup sections could be more condensed. | 2 / 3 |
Actionability | Provides fully executable commands throughout with specific examples for every operation. Commands are copy-paste ready with clear argument documentation and real-world usage patterns. | 3 / 3 |
Workflow Clarity | Multi-step processes like 'Create and verify an issue' and 'Move issue through workflow' include explicit verification steps. The check command provides validation before operations, and examples show the verify-after-action pattern. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external files (scriptrunner.md, examples.md, jql-reference.md). Content is organized from setup through commands to troubleshooting with one-level-deep references. | 3 / 3 |
Total | 11 / 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.
Table of Contents
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.