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.
89
87%
Does it follow best practices?
Impact
95%
1.48xAverage score across 3 eval scenarios
Passed
No known issues
CLI multi-line issue creation
Backend detection present
0%
100%
CLI fallback or error
0%
100%
/tmp file for multi-line body
66%
100%
cat substitution for body
0%
100%
No raw inline multi-line -b
100%
100%
--no-input with all fields
100%
100%
Issue type flag present
100%
100%
Project key flag present
100%
100%
Summary flag present
100%
100%
Temp file cleanup
100%
100%
Creates multiple issues
100%
100%
Script is valid bash
100%
100%
Safe MCP assignment and transition workflow
lookupJiraAccountId call
41%
100%
Account ID used for assignment
100%
100%
Fetch before update
100%
100%
getTransitionsForJiraIssue call
58%
100%
transitionId used (not name)
100%
100%
Show changes before executing
12%
25%
Approval step before modifying
0%
12%
Comment added after update
100%
100%
Verify after applying
100%
100%
Backend detection present
14%
71%
Handles multiple tickets
100%
100%
MCP issue linking and bulk modification safety
Uses jira-link-issues script
0%
100%
Correct script path
0%
100%
Correct script argument order
0%
100%
Per-ticket approval before bulk changes
100%
100%
Fetch before transition
50%
100%
Get transitions before transitioning
100%
100%
Comment added explaining change
100%
100%
Watcher impact acknowledged
87%
100%
Link type correctly specified
50%
100%
Verify links created
100%
100%
6768672
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.