jira-read-ticket

Retrieve descriptions, comments, and metadata from Jira Cloud tickets.

11|2|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/bkircher/skills --skill jira-read-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-read-ticket
Source: https://github.com/bkircher/skills/tree/main/jira-read-ticket
Command: npx skills add https://github.com/bkircher/skills --skill jira-read-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill streamlines the process of retrieving information from Jira, eliminating the need to manually navigate the Jira interface or construct complex API calls.

Core Features & Use Cases

  • Fetch Ticket Details: Retrieve the description, comments, and other key information for any Jira ticket.
  • Automated Data Retrieval: Use in conjunction with other AI agents to provide context from Jira tickets for tasks like bug triaging or feature planning.
  • Use Case: When a user mentions a Jira ticket like "ABC-123", this skill can automatically fetch and present the ticket's description and recent comments.

Quick Start

Use the jira-read-ticket skill to fetch the description for Jira ticket 'PROJ-456'.

Frequently Asked Questions about jira-read-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve Jira ticket details automatically without navigating the interface?

To retrieve Jira ticket details automatically, you can fetch descriptions, comments, and metadata directly via API. This provides structured data for issue analysis and eliminates manual navigation of the Jira Cloud interface.

What is the best way to fetch Jira issue comments and descriptions for automated workflows?

Fetching Jira issue comments and descriptions for automated workflows is best handled by extracting structured data from Jira Cloud tickets. This enriches AI agent context for tasks like bug triaging and feature planning without complex API calls.

Do I need Atlassian API credentials to access Jira ticket information programmatically?

Yes, you need valid Atlassian API credentials and your Jira URL configured as environment variables to access Jira ticket information. This authentication is required to securely retrieve detailed issue metadata and comments.

Can I use a Jira ticket ID to pull context for bug triaging and feature planning?

Yes, you can use a Jira ticket ID like 'PROJ-456' to pull context for bug triaging and feature planning. The system automatically fetches and presents the ticket's description and recent comments for immediate analysis.

What limitations exist when retrieving Jira Cloud ticket metadata through an API?

A limitation of retrieving Jira Cloud ticket metadata is the strict dependency on valid Atlassian API credentials configured as environment variables. Without this setup, automated workflows cannot fetch ticket descriptions or associated comments.