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.
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 a well-crafted skill description that excels across all dimensions. It provides specific actions, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and has clear distinctiveness through Jira/Atlassian-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' - covers searching, creating, updating, and workflow management. | 3 / 3 |
Completeness | Clearly answers both what ('Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows') AND when ('Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Jira tickets', 'backlog', 'sprints', 'bugs', 'Atlassian', 'project management', 'JQL queries' - these are terms users naturally use when working with Jira. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers specific to Jira/Atlassian ecosystem - 'JQL queries', 'Jira tickets', 'sprints', 'Atlassian' are highly specific and unlikely to conflict with other project management or ticketing skills. | 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 in setup/configuration sections that could be tightened. The skill excels at providing executable examples and clear validation patterns for Jira operations.
Suggestions
Condense the Installation and Authentication sections - Claude doesn't need explanations of what environment variables are or how to add them to shell config files
The 'How Defaults Work' section could be reduced to a brief inline note since the behavior is standard and intuitive
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations (e.g., explaining what each config option means when Claude would understand from context). The installation and setup sections could be more condensed, and some command descriptions repeat information. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands throughout, concrete examples for every command, specific argument documentation, and copy-paste ready code blocks. The examples section shows complete workflows. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation steps. The 'Create and verify an issue' and 'Move issue through workflow' examples show proper check-then-act patterns with verification steps after operations. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview sections and appropriate references to external files (permissions.md, scriptrunner.md, examples.md, jql-reference.md). References are one level deep and clearly signaled with descriptive links. | 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.
Reviewed
Table of Contents