jira-cli Skill
What it does
🔥 Feature-rich interactive Jira command line.
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category Other
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/ankitpokhrel-jira-cli)Similar Skills
Same kind of work, ordered like the Skills list
| This one jira-cli | llmfit | claude-video | VideoCaptioner | patent-disclosure-skill | |
|---|---|---|---|---|---|
| Maker | ankitpokhrel | AlexsJones | bradautomates | WEIFENG2333 | handsomestWei |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 6,075 | 39,004 | 20,889 | 16,539 | 13,468 |
| Last code change | Oct 17, 2026 | Nov 12, 2026 | Sep 25, 2026 | Sep 12, 2026 | Nov 15, 2026 |
| License | MIT | MIT | MIT | GPL-3.0 | MIT |
1 skills (instruction sets) by ankitpokhrel that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodexOpenCode
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account ankitpokhrel (person), 14 years old
- Use and upkeep
★ 6,075 stars · code last changed Oct 17, 2026
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 9b593fd (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Files are byte-for-byte the same as on GitHub at commit 9b593fd · View on GitHub ↗
Plain text files, no programs
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
Look inside before downloading
All 2 files · 5 KB
SKILL.md4 KBLICENSE1 KB
Download jira-cli.zip
Open Skills on claude.ai and upload
+Create skillUpload a skillpick jira-cli.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /jira-cli or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/ankitpokhrel/jira-cli.git /tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd/skills/jira-cli' ~/.claude/skills/jira-cliRestart Claude Code, then type /jira-cli or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the jira-cli folder at ~/.agents/skills/jira-cli
~ is your home folder ($HOME)
Without Terminal: download the ZIP, unzip it and move the jira-cli folder to ~/.agents/skills
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/ankitpokhrel/jira-cli.git /tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd/skills/jira-cli' ~/.agents/skills/jira-cli
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/ankitpokhrel/jira-cli.git /tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd/skills/jira-cli' ~/.agents/skills/jira-cliRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick jira-cli
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/ankitpokhrel/jira-cli.git /tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-ankitpokhrel-jira-cli-9b593fd/skills/jira-cli' ~/.cursor/skills/jira-cliIn Cursor’s Agent chat, type / and pick jira-cli
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
3,941 characters · Open the full file on GitHub
---
name: jira-cli
description: Use Jira-CLI to search, inspect, create, or update Jira issues and related project data. Covers machine-readable output, configuration metadata, command discovery, and safe execution.
---
# Jira CLI
Use this skill when operating Jira through the `jira` command. Start with `jira --help`, then inspect the relevant command and subcommand help (for
example, `jira issue list --help`) before using them. The installed CLI's help is the source of truth for its available commands, flags, and syntax; it also
contains command-specific examples. This skill adds agent-oriented safety guidance and useful workflow patterns that may not be obvious from the flags.
## Prefer machine-readable output
List commands are interactive by default. When reading data programmatically, prefer an output format intended for parsing:
```sh
# JSON
jira issue list --raw
# Plain text, optionally selecting fields and omitting headers
jira issue list --plain --columns key,summary --no-headers
# CSV
jira issue list --csv
```
Use `--raw` when supported and JSON is needed. Otherwise, use `--plain` with `--columns` and `--no-headers` to minimize parsing ambiguity.
## Configuration and fields
The default configuration file is:
```text
$XDG_CONFIG_HOME/.jira/.config.yml
```
When `XDG_CONFIG_HOME` is unset, it is:
```text
~/.config/.jira/.config.yml
```
The configuration file can be used as a data source. It contains the configured project, issue types, and custom field definitions. In particular, inspect
`issue.types` and `issue.fields.custom` before constructing `create`, `edit`, or `--custom` commands.
Use `--config/-c` or `JIRA_CONFIG_FILE` to select another configuration file.
This metadata is created during `jira init` and, over time, can become out of sync with Jira. Refreshing the configuration with `jira init` changes local
configuration. NEVER do it without obtaining explicit confirmation first.
For custom fields, use `--custom key=value`. The key is derived from the configured field name in lowercase with words separated by hyphens (for example,
`Story Points` becomes `story-points`). The expected value format depends on the field type; array values are comma-separated. Only use fields present in the
configuration, and inspect their schema rather than guessing the format.
Do not guess a field name, ID, allowed value, or issue type when it is missing or inconsistent. Instead, use another authorized source of truth, such as the Jira
UI or API. Some error messages contain relevant data; for instance, when `jira issue move` fails due to an invalid transition state, it lists available
states in the error output. If everything fails, ask the user.
## Useful JQL patterns
Use `jira issue list --jql` (`-q`) when the built-in filters are insufficient. For example, raw JQL can search across multiple projects, use a saved filter, or
approximate a backlog query:
```sh
# Issues in either project
jira issue list -q "project IN (PRJ1, PRJ2)"
# Issues matching a saved Jira filter
jira issue list -q "filter='my saved filter'"
# Backlog-style issues (adapt statuses and issue types to the project workflow)
jira issue list -s~Done -q "sprint is empty and issuetype not in (Epic, Sub-task)" --order-by rank --reverse
```
When the JQL itself contains a project condition, it takes precedence over `--project` (`-p`); do not expect `-p` to further restrict that query.
## Safe execution
- NEVER expose `JIRA_API_TOKEN` or config credentials; `--debug` may print auth headers.
- ALWAYS confirm destructive actions and externally visible changes the user did not explicitly request.
- Read an issue before updating it when its current state matters. Verify consequential or uncertain updates.
- Use `jira <command> [<subcommand>] --help` for flags, requirements, and examples. Supply explicit arguments and use `--no-input` when supported.
- Cache useful discoveries for the session.
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 6,075
- Maker
- ankitpokhrel
- License
- MIT
- Last code change
- Oct 17, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- atlassian, cli, cli-app, command-line, command-line-tool, console, go, golang, golang-cli, jira, jira-cli, made-in-nepal