jira-issue
Retrieves Jira issue details using a key and displays them in formatted markdown, bypassing raw JSON noise.
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.Key capabilities
- →Extract Jira issue keys from messages
- →Fetch Jira issue details
- →Format Jira output as markdown
- →Present Jira issue information directly
- →Report script errors verbatim
How it works
The skill extracts a Jira issue key from the user's message and runs a Python script to fetch and format the issue details as markdown.
Inputs & outputs
When to use jira-issue
- →View ticket requirements before starting development
- →Check the current status of a bug or task
- →Get assignee information for a specific Jira issue
- →Reference ticket details during a code review
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
When not to use it
- →When the user asks to summarize or reformat the output further without specific instructions
- →When calling the Atlassian MCP server for Jira issue lookups
Prerequisites
Limitations
- →Credentials are read from a .env file in the project root
- →The script prints an ERROR: line if an error occurs
- →Do not call the Atlassian MCP server for issue lookups
How it compares
This skill provides clean, formatted markdown output for Jira issues directly, avoiding raw JSON or ADF noise from other tools.
Compared to similar skills
jira-issue side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| jira-issue (this skill) | 0 | 2mo | Review | Beginner |
| linear | 10 | 2mo | No flags | Beginner |
| github-manage | 6 | 9mo | Review | Beginner |
| task-management | 16 | 5mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
github-manage
matteocervelli
Manage operations concerning GitHub on behalf of user
task-management
anthropics
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
spec-to-backlog
atlassian
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
jira
davila7
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.
github-issues
github
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.