← Back to Skills Marketplace
JIRA
by
Jonathan Rhyne
· GitHub ↗
· v1.3.3
9218
Downloads
16
Stars
0
Active Installs
7
Versions
Install in OpenClaw
/install jira
Description
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira...
Usage Guidance
Install only if you trust the publisher and intend agents to work with your Jira account. Use least-privilege Jira credentials, avoid giving broad project-admin tokens, require explicit confirmation before any create/update/move/assign/comment/sprint action, and prefer the scoped MCP/CLI path over raw curl commands with API tokens.
Capability Analysis
Type: OpenClaw Skill
Name: jira
Version: 1.3.3
The skill is classified as suspicious due to its extensive use of shell command execution and direct network calls involving sensitive credentials, which present significant prompt injection vulnerabilities. Specifically, `SKILL.md` and `references/commands.md` instruct the agent to execute various `jira` CLI commands, often leveraging shell features like command substitution (`$(jira me)`) and temporary file creation (`cat > /tmp/jira_body.md`). Furthermore, `references/mcp.md` includes a `curl` command that directly uses `JIRA_USER`, `JIRA_API_TOKEN`, and `JIRA_BASE_URL` environment variables for API interaction. While these actions are intended for legitimate Jira operations, the broad access to shell and network with credentials creates a high-risk attack surface if the agent's instructions are subverted.
Capability Assessment
Purpose & Capability
The documented capabilities fit a Jira integration: querying issues plus creating, moving, assigning, commenting, sprint changes, CLI use, MCP use, and REST fallbacks are purpose-aligned.
Instruction Scope
The skill trigger language reportedly includes generic words like issue and ticket, and the references document live state-changing Jira actions without clear confirmation boundaries or prominent separation from read-only operations.
Install Mechanism
No artifact-backed evidence indicates deceptive installation, hidden package execution, or unrelated install-time behavior.
Credentials
Using Jira credentials, shell commands, CLI workflows, and network calls is coherent for Jira work, but raw curl/API-token examples and shell fallbacks broaden the execution surface beyond a safer scoped MCP path.
Persistence & Privilege
No hidden persistence was shown, but the skill can operate with Jira account privileges and includes non-interactive mutation examples such as ticket creation with --no-input.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install jira - After installation, invoke the skill by name or use
/jira - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.3
Scanner hardening: make Jira env vars optional (REST fallback only) to align with multi-backend CLI/MCP design
v1.3.2
Scanner hardening: align _meta version, add provenance fields, remove local helper-path assumptions from docs
v1.3.1
Hardening correction: publish MCP docs without user-local helper-script path references
v1.3.0
Hardening pass: remove user-local helper-script path references from MCP docs and keep requirements consistent
v1.2.0
Fix suspicious flag: declare all required env vars (JIRA_API_TOKEN, JIRA_USER, JIRA_BASE_URL), fix reference to non-existent helper script
v1.1.0
Added structured openclaw metadata: jira binary + JIRA_API_TOKEN env requirement
v1.0.0
Initial release – manage Jira from the command line using jira-cli.
- Search, create, update, and transition Jira issues directly via terminal commands.
- Manage sprints, boards, epics, and projects with simple CLI options.
- Includes setup instructions and best practices for API token, configuration, and workflow.
- Supports custom output formats for scripting and automation.
- Adds safeguards—confirm changes with the user before creating, editing, or transitioning issues.
Metadata
Frequently Asked Questions
What is JIRA?
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira... It is an AI Agent Skill for Claude Code / OpenClaw, with 9218 downloads so far.
How do I install JIRA?
Run "/install jira" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is JIRA free?
Yes, JIRA is completely free (open-source). You can download, install and use it at no cost.
Which platforms does JIRA support?
JIRA is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created JIRA?
It is built and maintained by Jonathan Rhyne (@jdrhyne); the current version is v1.3.3.
More Skills