jira-reader

Fetch Jira ticket details and execute JQL searches via CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pacvue/devflow-cursor --skill jira-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-reader
Source: https://github.com/Pacvue/devflow-cursor/tree/main/.cursor/skills/jira-reader
Command: npx skills add https://github.com/Pacvue/devflow-cursor --skill jira-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) components.

What problem does it solve?

Jira read-only queries enable teams to fetch ticket details and perform JQL searches without risking changes to issues, providing quick access to current state and metadata.

Core Features & Use Cases

  • Read-only ticket details: fetch a single Jira issue by its key and display fields such as summary, status, and assignee.
  • JQL-based searches: run queries to discover multiple issues and summarize key fields.
  • Local CLI execution: uses scripts/jira-query.py for reproducible, scriptable queries; supports output in text or JSON; requires Atlassian credentials via environment variables.

Quick Start

Ask the system to fetch a Jira ticket by key or perform a JQL search using the jira-query.py CLI.

Frequently Asked Questions about jira-reader

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

FAQPage Schema
How do I run read-only Jira queries to fetch ticket details without modifying issues?

To run read-only Jira queries, you use a local CLI script that fetches ticket details and executes JQL searches without modifying data. It connects to the Jira REST API using your Atlassian credentials to safely retrieve current state and metadata.

What is the best way to search multiple Jira issues using JQL across a project scope?

The best way to search multiple Jira issues using JQL is via the local CLI script, which executes queries to discover issues across typical project scopes. It summarizes key fields such as summary, status, and assignee in text or JSON output.

Do I need Atlassian credentials to perform single-ticket lookups with the Jira REST API?

Yes, you need Atlassian credentials configured via environment variables to perform single-ticket lookups. The CLI script requires these credentials to authenticate with the Jira REST API and securely fetch the specified issue key.

Can I use a Python script to get Jira ticket details and output the results in JSON?

Yes, you can use the provided Python script to get Jira ticket details and output the results in JSON. The local CLI execution supports both text and JSON formats, allowing for reproducible and scriptable query outputs.

Are there limitations to using read-only Jira queries for discovering issues?

A key limitation of read-only Jira queries is that they cannot modify data, restricting usage to fetching ticket details and performing searches. Queries are executed with defined fields and timeouts to prevent unintended changes to issues.