show-jira-issue
SolidUse this skill when the user asks about a specific Jira issue by key (e.g. PROJ-123, ENG-456) — for viewing the description, status, comments, transitions, or any other field. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' a key, or asks any direct question about an issue they reference. Do NOT trigger when an issue key appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- atomicinnovation
- Repository
- atomicinnovation/accelerator
- Created
- 2 months ago
- Last Updated
- today
- Language
- HTML
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
search-jira-issues
Use this skill whenever the user wants to search, list, or filter Jira tickets — by assignee, status, label, project, type, component, reporter, parent, or free text — even if they say 'find', 'show me', 'what's open', 'list my tickets', or similar phrasing rather than 'search Jira'. Composes safe JQL from structured flags, executes a paginated search against a Jira Cloud tenant, and renders a summary table of the results. Supports --render-adf to convert ADF descriptions to Markdown inline. Prefer this skill over raw JQL whenever the user's intent maps to a structured flag.
jira
This skill should be used when the user mentions a Jira ticket key (e.g. SOX-1234, DEVTOOLS-456), asks about ticket details, or wants to look up a Jira issue. Fetches live ticket data from Jira Cloud.
create-jira-issue
Use this skill only when the user explicitly invokes /create-jira-issue to create a new Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts a project key, issue type, summary, optional Markdown body, and optional fields (assignee, priority, labels, components, parent, custom fields). Converts the body to ADF, shows a payload preview, requires explicit confirmation, then POSTs to Jira and returns the new issue key.