How do I install the 022 Tooling Jira skill?

Run npx skillmds add majiayu000/022-tooling-jira in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 022 Tooling Jira safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 022 Tooling Jira?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 022 Tooling Jira free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 022 Tooling Jira?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

022 Tooling Jira by majiayu000 — Agent Skill

Name: 022 Tooling Jira
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

022 Tooling Jira

Use when you need the Jira CLI (`jira`) to verify installation, configure Jira Cloud access, list issues (all or by JQL) as markdown tables, fetch issue descriptions and comments for analysis, or hand off to @014-agile-user-story when creating user stories from Jira threads. Uses an interactive install gate - if `jira` is missing, ask whether to show installation guidance before any issue commands. Part of the skills-for-java project

majiayu000 257e7f2 2 files · 3.2 KB Updated Sep 9, 2026 567 repo stars

File contents

Jira CLI - issues, workflows, and discussion for analysis

Use jira to work with Jira issues: first run an interactive check - if jira is not installed, stop, ask whether the user wants installation guidance, wait for an answer, then continue. When jira is available, validate configuration, list issues with optional JQL filters, render markdown tables from command output, load full issue descriptions and comment threads for analysis, and when the user wants user stories plus Gherkin, chain to @014-agile-user-story using Jira issue content as source material.

What is covered in this Skill?

Interactive install gate: ask before assuming jira is installed; offer installation guidance only when the user agrees
Install/config checks (jira version, jira configure)
Jira Cloud context (site URL, account email, API token handled by CLI prompts)
Issue lists: basic list and JQL-backed list queries
Deep reads: issue detail and comments for requirement analysis
Core actions: create, assign, transition, and add comments

Constraints

Do not fabricate issue data; use only jira output (or explicitly agreed Jira REST API responses). Never print API tokens or secrets.

INTERACTIVE GATE: If jira is missing, stop, ask whether the user wants installation guidance, wait - do not skip to issue listing
FIRST (after gate): Verify jira is available before issuing subcommands
CONFIG: Ensure Jira CLI is configured before private workspace operations
TABLES: Prefer markdown pipe tables for issue list summaries
THREAD: For analysis, include description and all comments (or explicitly summarize with omissions noted)
014: For user stories from Jira issues, use @014-agile-user-story and align answers with Jira-sourced text

When to use this skill

jira issue list
List Jira issues
Jira JQL issue query
jira issue view comments
Jira CLI issue workflow

---name: 022-tooling-jiradescription: Use when you need the Jira CLI (`jira`) to verify installation, configure Jira Cloud access, list issues (all or by JQL) as markdown tables, fetch issue descriptions and comments for analysis, or hand off to @014-agile-user-story when creating user stories from Jira threads. Uses an interactive install gate - if `jira` is missing, ask whether to show installation guidance before any issue commands. Part of the skills-for-java projectlicense: Apache-2.0---# Jira CLI - issues, workflows, and discussion for analysis Use **`jira`** to work with Jira issues: **first** run an **interactive** check - if `jira` is not installed, **stop**, ask whether the user wants installation guidance, **wait** for an answer, then continue. When `jira` is available, validate configuration, list issues with optional JQL filters, render **markdown tables** from command output, load **full issue descriptions and comment threads** for analysis, and when the user wants user stories plus Gherkin, **chain to `@014-agile-user-story`** using Jira issue content as source material. **What is covered in this Skill?** - **Interactive** install gate: ask before assuming `jira` is installed; offer installation guidance only when the user agrees - Install/config checks (`jira version`, `jira configure`) - Jira Cloud context (site URL, account email, API token handled by CLI prompts) - Issue lists: basic list and JQL-backed list queries - Deep reads: issue detail and comments for requirement analysis - Core actions: create, assign, transition, and add comments ## Constraints Do not fabricate issue data; use only `jira` output (or explicitly agreed Jira REST API responses). Never print API tokens or secrets. - **INTERACTIVE GATE**: If `jira` is missing, **stop**, ask whether the user wants installation guidance, **wait** - do not skip to issue listing - **FIRST** (after gate): Verify `jira` is available before issuing subcommands - **CONFIG**: Ensure Jira CLI is configured before private workspace operations - **TABLES**: Prefer markdown pipe tables for issue list summaries - **THREAD**: For analysis, include description and all comments (or explicitly summarize with omissions noted) - **014**: For user stories from Jira issues, use `@014-agile-user-story` and align answers with Jira-sourced text ## When to use this skill - jira issue list - List Jira issues - Jira JQL issue query - jira issue view comments - Jira CLI issue workflow

Frequently asked questions