Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
86
86%
Does it follow best practices?
Impact
79%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Safe issue transitioning
Backend detection
100%
0%
Fetch active sprint
100%
100%
Fetch current issue status
100%
100%
Transition discovery per issue
100%
13%
No hardcoded transition name
80%
0%
Pre-execution summary
100%
100%
User confirmation gate
100%
100%
Bulk-modify approval noted
50%
100%
Post-transition verification
12%
0%
Intermediate state awareness
0%
100%
Show command before run
50%
0%
MCP assignment and description editing
Backend detection step
20%
40%
Account ID lookup first
66%
100%
No display name assignment
100%
100%
Fetch issue before update
40%
100%
Show original description
100%
100%
Preserve existing description content
100%
100%
Approval before bulk assign
62%
12%
Correct MCP tool names
50%
100%
Post-assignment verification
100%
100%
Authentication guidance
0%
0%
Multi-line CLI issue creation
Backend detection
100%
100%
Temp file for multi-line
100%
100%
No inline multi-line string
100%
100%
Read /tmp file in command
83%
100%
Required fields check
58%
100%
Show command before run
100%
100%
Correct issue type flag
100%
100%
Success verification
100%
100%
Sample report quality
100%
100%
Multi-line handling explained
80%
100%
3027f20
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.