jira-cli Skill
summary: Feature-rich interactive CLI for Atlassian Jira. Provides issue management, epic/sprint navigation, transitions, and more from the command line.
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
jira-cli is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around integration skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is Generic Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in dl-alexandre/cli-installer-toolkit, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
--- name: jira-cli summary: Feature-rich interactive CLI for Atlassian Jira. Provides issue management, epic/sprint navigation, transitions, and more from the command line. triggers: - jira-cli - jira command line - jira issue list - jira issue create - jira sprint - jira epic - atlassian jira cli - ticket management cli - jira from terminal - move jira ticket - transition jira issue --- # Jira CLI ## Overview JiraCLI is an interactive command line tool for Atlassian Jira that helps avoid the Jira UI for common tasks. It provides an interactive TUI for browsing issues, creating tickets, managing sprints/epics, transitioning issues, and more. **Repository**: https://github.com/ankitpokhrel/jira-cli **Doc Version**: v1.7.0 (Aug 31, 2025) ### Supported Platforms | Platform | Support | |----------|---------| | **OS** | Linux, macOS, FreeBSD, NetBSD, Windows | | **Jira** | Jira Cloud, Jira Server (on-premise) | ## When Not to Use This Skill - **Bulk data exports**: Use Jira's native CSV/JSON export or REST API directly for large data migrations - **Jira administration**: User management, permissions, and scheme configuration require the Jira admin UI - **Complex JQL reporting**: For dashboards and advanced reporting, use Jira's built-in gadgets or third-party BI tools - **Webhook configuration**: Must be done through Jira settings - **Custom field type creation**: Requires admin UI access ## Installation ### Homebrew (macOS/Linux) ```bash brew install ankitpokhrel/jira-cli/jira-cli ``` ### Go Install ```bash go install github.com/ankitpokhrel/j ...