JI
jira-issue
Fetch and display a Jira issue with clean, formatted output. Use this skill whenever the user mentions a Jira issue key (e.g., ABC-123, PROJ-456), asks about a story, ticket, bug, or task in Jira, or wants to look up requirements, status, assignee, description, or any other details for a Jira item.
Install
mkdir -p .claude/skills/jira-issue && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15259" && unzip -o skill.zip -d .claude/skills/jira-issue && rm skill.zipInstalls to .claude/skills/jira-issue
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Fetch and display a Jira issue with clean, formatted output. Use this skill whenever the user mentions a Jira issue key (e.g., ABC-123, PROJ-456), asks about a story, ticket, bug, or task in Jira, or wants to look up requirements, status, assignee, description, or any other details for a Jira item. Always use this skill instead of the Atlassian MCP server for Jira issue lookups.381 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
About this skill
Jira Issue Skill
Fetch a Jira issue by its key and return clean, formatted markdown — no raw JSON, no ADF noise.
Steps
- Extract the issue key from the user's message (e.g.,
ABC-123) - Run the fetch script:
python .github/skills/jira-issue/scripts/fetch_jira.py <ISSUE-KEY>
- Present the output directly — it is already formatted as markdown. Do not summarize or reformat it further unless the user asks.
Notes
- Credentials are read from a
.envfile in the project root. Required variables:JIRA_USER_EMAIL— the email associated with the API tokenJIRA_API_TOKEN— generated at https://id.atlassian.com/manage-profile/security/api-tokens
- If the script prints an
ERROR:line, report it verbatim so the user can diagnose it - Do not call the Atlassian MCP server for issue lookups — always use this script