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
Cross-project JQL with statusCategory
Uses skill script
0%
100%
statusCategory not status
100%
100%
Three statusCategory values
100%
100%
No hardcoded status names
100%
100%
max-results flag used
0%
100%
fields flag used
0%
100%
check command present
0%
100%
Multi-project query
100%
100%
Valid shell script
100%
100%
JQL ORDER BY
100%
100%
Without context: $0.2029 · 1m 4s · 14 turns · 69 in / 3,570 out tokens
With context: $0.3558 · 1m 9s · 20 turns · 896 in / 3,569 out tokens
Configuration defaults setup
Correct config path
37%
100%
jql_scope configured
0%
100%
security_level configured
0%
100%
max_results configured
50%
100%
fields list configured
60%
100%
BACKEND project defaults
60%
100%
INCIDENTS project defaults
60%
100%
check command in script
0%
100%
config show command
0%
100%
Auth placeholders present
87%
100%
YAML structure valid
66%
100%
Without context: $0.2568 · 1m 12s · 18 turns · 24 in / 4,079 out tokens
With context: $0.4418 · 1m 22s · 23 turns · 26 in / 3,979 out tokens
Private comments and transitions
Uses skill script
0%
100%
transitions list step
0%
100%
transitions do command
0%
100%
Transition with comment
0%
100%
Transition security level
0%
100%
issue comment command
0%
100%
Comment security level
0%
100%
Issue key parameterized
100%
100%
Valid shell script
100%
100%
Does NOT use public comment
100%
100%
Without context: $0.3955 · 1m 44s · 25 turns · 29 in / 5,156 out tokens
With context: $0.3192 · 1m 17s · 21 turns · 312 in / 3,634 out tokens
ScriptRunner hierarchy and link queries
Uses skill script
100%
100%
check command present
62%
100%
issuesInEpics used
0%
100%
subtasksOf used
0%
100%
linkedIssuesOf used
58%
100%
hasLinkType used
0%
100%
Date filter for performance
100%
100%
Epic key parameterized
100%
100%
Output redirected to file
100%
100%
Valid shell script
100%
100%
Without context: $0.2076 · 1m 4s · 15 turns · 16 in / 3,691 out tokens
With context: $0.5019 · 1m 32s · 25 turns · 1,363 in / 5,164 out tokens
Contributor search and collaboration analysis
Uses skill script
0%
100%
--contributor flag used
0%
100%
--project scope on contributor search
0%
100%
issue get --contributors used
0%
100%
collaboration epics command
0%
100%
--min-contributors 3
0%
100%
--max-results on collaboration
0%
100%
Output saved to file
100%
100%
Without context: $0.5902 · 2m 38s · 31 turns · 100 in / 8,968 out tokens
With context: $0.3115 · 56s · 19 turns · 1,755 in / 2,814 out tokens
ScriptRunner user activity audit with accountId lookup
Uses skill script
100%
100%
accountId lookup step
70%
100%
commentedByUser query
35%
100%
transitionedBy query
33%
100%
lastUpdatedBy query
25%
100%
Date filter applied
100%
100%
Multi-project scope
100%
100%
Two-step workflow documented
100%
100%
Output saved to file
100%
100%
Without context: $0.3654 · 1m 39s · 23 turns · 62 in / 5,540 out tokens
With context: $0.5379 · 2m · 20 turns · 1,183 in / 6,639 out tokens
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.