netresearch/jira-skill / skills/jira-communication
jira-communication
FlaggedUse when handling Jira issues, sprints, boards, links, fields, worklogs, attachments, or users, or on any Jira intent without a key ("create/find a ticket", "pick a project"). Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when MCP Atlassian tools fail or are unavailable for Jira Server/DC.
evals/evals.json
View on GitHub[
{
"name": "search_open_bugs_assigned_to_me",
"prompt": "Search for all open bugs in project PROJ assigned to me",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-search\\.py.*query"
},
{
"type": "content",
"pattern": "assignee\\s*=\\s*currentUser\\(\\)"
},
{
"type": "content",
"pattern": "type\\s*=\\s*Bug"
},
{
"type": "content",
"pattern": "project\\s*=\\s*PROJ"
}
]
},
{
"name": "create_bug_report_login_failure",
"prompt": "Create a bug report in project PROJ for a login failure - users get a 500 error when clicking the login button",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-create\\.py"
},
{
"type": "content",
"pattern": "(--type|--issuetype).*(Bug|bug)"
},
{
"type": "content",
"pattern": "--project.*PROJ"
}
]
},
{
"name": "transition_and_comment",
"prompt": "Transition PROJ-123 to In Progress and add a comment saying work has started",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-transition\\.py.*do.*PROJ-123"
},
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-comment\\.py.*add.*PROJ-123"
},
{
"type": "content",
"pattern": "In Progress"
}
]
},
{
"name": "log_work_with_description",
"prompt": "Log 2 hours of work on PROJ-456 with description 'Implemented API endpoint'",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-worklog\\.py.*add.*PROJ-456.*2h"
},
{
"type": "content",
"pattern": "(--comment|--description).*Implemented API endpoint"
}
]
},
{
"name": "add_multiline_comment_via_stdin",
"prompt": "Add this comment to PROJ-789:\n\nh2. Status Update\n\n* Deployment completed\n* Tests passing\n\nThis is multiline Jira wiki markup — use stdin piping to preserve formatting.",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-comment\\.py.*add\\s+PROJ-789\\s+-"
},
{
"type": "content",
"pattern": "(\\bcat\\b|\\|.*jira-comment|\\bstdin\\b|<<)"
},
{
"type": "content",
"pattern": "Status Update"
}
]
},
{
"name": "add_simple_comment_inline",
"prompt": "Add a comment to PROJ-100 saying 'Fixed in commit abc123'",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-comment\\.py.*add.*PROJ-100.*Fixed in commit"
},
{
"type": "content",
"pattern": "Fixed in commit abc123"
}
]
},
{
"name": "read_issue_status_and_assignee",
"prompt": "What's the status and assignee of PROJ-135?",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-issue\\.py.*get\\s+PROJ-135"
},
{
"type": "content",
"pattern": "(status|assignee)"
}
]
},
{
"name": "get_issue_as_json",
"prompt": "Get PROJ-135 details as JSON",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-issue\\.py.*--json.*get\\s+PROJ-135|jira-issue\\.py.*get\\s+PROJ-135.*--json"
},
{
"type": "content",
"pattern": "--json"
}
]
},
{
"name": "update_issue_priority_field",
"prompt": "Change the priority of PROJ-135 to Critical",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-issue\\.py.*update\\s+PROJ-135"
},
{
"type": "content",
"pattern": "--priority.*Critical"
}
]
},
{
"name": "identify_current_jira_user",
"prompt": "Which Jira user am I logged in as?",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-user\\.py.*me"
},
{
"type": "content",
"pattern": "jira-user\\.py"
}
]
},
{
"name": "create_issue_link_blocks",
"prompt": "Link PROJ-100 as blocking PROJ-200 and show me all links on PROJ-100",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-link\\.py.*create"
},
{
"type": "content",
"pattern": "(Blocks|blocks).*PROJ-200|PROJ-100.*PROJ-200"
},
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-link\\.py.*list\\s+PROJ-100"
}
]
},
{
"name": "add_watcher_to_issue",
"prompt": "Add asmith as a watcher on PROJ-135",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-watchers\\.py.*add\\s+PROJ-135\\s+asmith"
},
{
"type": "content",
"pattern": "asmith"
}
]
},
{
"name": "list_unreleased_versions",
"prompt": "List unreleased versions in project PROJ",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-version\\.py.*list\\s+PROJ"
},
{
"type": "content",
"pattern": "(--status.*unreleased|unreleased)"
}
]
},
{
"name": "upload_attachment_to_issue",
"prompt": "Attach the file /tmp/eval-report.txt to PROJ-135",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-attachment\\.py.*add\\s+PROJ-135"
},
{
"type": "content",
"pattern": "/tmp/eval-report\\.txt"
}
]
},
{
"name": "download_all_attachments_from_issue",
"prompt": "Download all attachments from PROJ-135 into ./attachments",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-attachment\\.py.*download-all\\s+PROJ-135"
},
{
"type": "content",
"pattern": "(\\./)?attachments"
}
]
},
{
"name": "create_ticket_from_intent_without_key",
"prompt": "We just decided on this work - please create a Jira task in project ACME titled 'Document the new export API'. I don't have an issue key yet.",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-create\\.py\\s+issue"
},
{
"type": "content",
"pattern": "(--type|--issuetype).*(Task|task)"
},
{
"type": "content",
"pattern": "ACME"
}
]
},
{
"name": "screen_fields_via_meta_not_raw_rest",
"prompt": "Setting customfield_12345 on a new ACME Task fails with 'not on the appropriate screen'. Find out which fields the ACME Task create screen accepts.",
"assertions": [
{
"type": "tool_use",
"tool": "Bash",
"pattern": "jira-fields\\.py\\s+(--json\\s+)?meta\\s+ACME"
},
{
"type": "content",
"pattern": "customfield_12345.*(screen|admin)|(screen|admin).*customfield_12345"
}
],
"samples": {
"passing": "uv run scripts/utility/jira-fields.py meta ACME Task lists the create screen; customfield_12345 is not on it, so a Jira admin has to add it to the ACME Task screen.",
"failing": [
"curl -s -H \"Authorization: Bearer $JIRA_PERSONAL_TOKEN\" \"$JIRA_URL/rest/api/2/issue/createmeta?projectKeys=ACME&expand=projects.issuetypes.fields\"",
"uv run scripts/utility/jira-fields.py meta ACME Task lists 12 fields."
]
}
}
]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |