jira-basics

Read Jira tickets, search with JQL, transition statuses, and add comments.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill jira-basics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-basics
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/kronen/skills/jira-basics
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill jira-basics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines interactions with Jira, allowing you to manage tickets, search for issues, update statuses, and add comments directly without leaving your current workflow.

Core Features & Use Cases

  • Ticket Management: Read ticket details, search using JQL, and transition statuses.
  • Collaboration: Add comments to tickets for team communication.
  • Use Case: When asked to check the status of a specific Jira ticket or find all open tickets assigned to a particular user, this Skill can perform those actions efficiently.

Quick Start

Check the status of the Jira ticket with key 'PROJ-123'.

Frequently Asked Questions about jira-basics

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

FAQPage Schema
How do I search Jira tickets using JQL without leaving my workflow?

Yes, you can transition Jira ticket statuses by using the Atlassian MCP server integration. The Skill requires adherence to ticket key format validation and transition confirmation protocols to safely move issues between workflow states.

What is needed to manage Jira issues and add comments via the Atlassian MCP server?

To find all open tickets assigned to a user, you can run a JQL query through the Atlassian MCP server. This Skill performs the search and retrieves matching issue tracking records efficiently for administrative review.

Can I transition Jira ticket statuses directly through an MCP server?

Yes, you can transition Jira ticket statuses by using the Atlassian MCP server integration. The Skill requires adherence to ticket key format validation and transition confirmation protocols to safely move issues between workflow states.

What is needed to manage Jira issues and add comments via the Atlassian MCP server?

To manage Jira issues and add comments, a configured Atlassian MCP server is required. The Skill relies on this server connection to read tickets, transition statuses, and post updates for team communication.

How do I check the status of a specific Jira ticket?

You can check the status of a specific Jira ticket by providing its ticket key, such as 'PROJ-123', to the Skill. It reads the ticket details via the Atlassian MCP server and returns the current tracking information.

Does Jira ticket management work without a configured Atlassian MCP server?

No, Jira ticket management through this Skill requires a configured Atlassian MCP server. Without this server connection, reading tickets, executing JQL searches, and transitioning statuses cannot be performed.