← Back to Skills Marketplace
kyjus25

Jira

by kyjus25 · GitHub ↗ · v1.0.2
cross-platform ✓ Security Clean
2825
Downloads
5
Stars
4
Active Installs
3
Versions
Install in OpenClaw
/install clawdbot-jira-skill
Description
Manage Jira issues, transitions, and worklogs via the Jira Cloud REST API.
README (SKILL.md)

Jira Skill

Work with Jira issues and worklogs from Clawdbot (search, status, create, log work, worklog summaries).

Setup

  1. Get your API key: https://id.atlassian.com/manage-profile/security/api-tokens
  2. Click "Create API Token"
  3. Set environment variables: 
    export JIRA_EMAIL="[email protected]"
export JIRA_API_TOKEN="your-api-token"
export JIRA_URL="https://your-domain.atlassian.net"
# Optional project scope (comma-separated). Empty = search all.
export JIRA_BOARD="ABC"

Requires curl, jq, bc, and python3.

Quick Commands

All commands live in {baseDir}/scripts/jira.sh.

  • {baseDir}/scripts/jira.sh search "timeout" [max] — fuzzy search by summary or key inside JIRA_BOARD
  • {baseDir}/scripts/jira.sh link ABC-123 — browser link for an issue
  • {baseDir}/scripts/jira.sh issue ABC-123 — quick issue details
  • {baseDir}/scripts/jira.sh status ABC-123 "In Progress" — move an issue (validates available transitions)
  • {baseDir}/scripts/jira.sh transitions ABC-123 — list allowed transitions
  • {baseDir}/scripts/jira.sh assign ABC-123 "name or email" — assign by user search
  • {baseDir}/scripts/jira.sh assign-me ABC-123 — assign to yourself
  • {baseDir}/scripts/jira.sh comment ABC-123 "text" — add a comment
  • {baseDir}/scripts/jira.sh create "Title" ["Description"] — create a Task in JIRA_BOARD
  • {baseDir}/scripts/jira.sh log ABC-123 2.5 [YYYY-MM-DD] — log hours (defaults to today UTC)
  • {baseDir}/scripts/jira.sh my [max] — open issues assigned to you
  • {baseDir}/scripts/jira.sh hours 2025-01-01 2025-01-07 — your logged hours by issue (JSON)
  • {baseDir}/scripts/jira.sh hours-day 2025-01-07 [name|email] — logged hours for a day grouped by user/issue; optional filter (name/email; also resolves to accountId)
  • {baseDir}/scripts/jira.sh hours-issue ABC-123 [name|email] — logged hours for an issue; optional filter (name/email; also resolves to accountId)

Command Reference

  • Search issues

    {baseDir}/scripts/jira.sh search "payment failure" [maxResults]

  • Issue link

    {baseDir}/scripts/jira.sh link ABC-321

  • Issue details

    {baseDir}/scripts/jira.sh issue ABC-321

  • Update status

    {baseDir}/scripts/jira.sh status ABC-321 "Done"

  • List transitions

    {baseDir}/scripts/jira.sh transitions ABC-321

  • Assign issue

    {baseDir}/scripts/jira.sh assign ABC-321 "Jane Doe"

  • Assign to yourself

    {baseDir}/scripts/jira.sh assign-me ABC-321

  • Add comment

    {baseDir}/scripts/jira.sh comment ABC-321 "Deployed to staging"

  • Create issue

    {baseDir}/scripts/jira.sh create "Fix auth timeout" "Users being logged out after 5m"

  • Log hours

    {baseDir}/scripts/jira.sh log PB-321 1.5 2025-01-18

  • My open issues

    {baseDir}/scripts/jira.sh my [maxResults]

  • Logged hours by issue (me)

    {baseDir}/scripts/jira.sh hours 2025-01-01 2025-01-05

  • Logged hours for a day (everyone)

    {baseDir}/scripts/jira.sh hours-day 2025-01-05

  • Logged hours for a day (user filter)

    {baseDir}/scripts/jira.sh hours-day 2025-01-05 "jane"

  • Logged hours for an issue

    {baseDir}/scripts/jira.sh hours-issue ABC-321 "jane"

Notes

  • Worklog commands use Jira's worklog/updated + worklog/list combo and may take a few seconds on large projects.
  • hours filters by JIRA_EMAIL; hours-day returns all users with totals per issue and user.
  • Outputs for hours commands are JSON for reuse in other tools.
  • Status transitions are validated against the server-provided transition list before applying.
Usage Guidance
This skill is a straightforward Jira CLI wrapper and appears to do only Jira API operations. Before installing: (1) Verify you trust the skill source and the included script (scripts/jira.sh) since it will send JIRA_EMAIL and JIRA_API_TOKEN to whatever JIRA_URL you set; use a token with minimal necessary permissions. (2) Confirm network access to the intended Atlassian domain and avoid pointing JIRA_URL to unknown endpoints. (3) Note the script uses standard tools (curl, jq, bc, python3) and also calls base64 (not declared) and common coreutils; ensure those exist in your environment. (4) If you do not want autonomous agent invocation of skills, change agent settings — autonomous invocation is the platform default. (5) If you have any doubt after review, consider creating a dedicated Jira API token with limited scope and rotate it if you remove the skill.
Capability Analysis
Type: OpenClaw Skill Name: clawdbot-jira-skill Version: 1.0.2 The OpenClaw AgentSkills skill bundle for Jira appears benign. It provides a set of shell commands to interact with the Jira Cloud REST API, requiring `JIRA_URL`, `JIRA_EMAIL`, and `JIRA_API_TOKEN` as environment variables for authentication. All network calls are directed to the configured Jira instance. The `scripts/jira.sh` file uses standard tools (`curl`, `jq`, `bc`, `python3`) and includes embedded Python scripts for data processing, which are well-defined and do not exhibit any malicious behavior. There is no evidence of data exfiltration, unauthorized execution, persistence mechanisms, or prompt injection attempts in `SKILL.md`.
Capability Assessment
✓ Purpose & Capability
Name/description (Jira issue/worklog management) match the required env vars (JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN) and the included script's API calls. The requested credentials are exactly those needed for Jira Cloud REST API access.
✓ Instruction Scope
SKILL.md and scripts instruct only Jira-related operations (search, transitions, comments, worklogs) and tell the agent to use the included script. The script only calls endpoints under the user-supplied JIRA_URL and does not reference unrelated system files, other services, or unexpected external endpoints.
✓ Install Mechanism
There is no install spec (instruction-only skill with an included script). Nothing is downloaded from remote URLs or written to unusual locations. This is the lower-risk installation pattern for skills.
ℹ Credentials
Requested env vars (JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN, optional JIRA_BOARD) are appropriate and proportionate. Note: the script constructs a Basic auth header using JIRA_EMAIL and JIRA_API_TOKEN and will send these to the configured JIRA_URL — that is expected behaviour but worth being aware of. Minor mismatch: the script uses the base64 utility but base64 is not listed in the SKILL.md required binaries; python3 is declared as required in metadata but its use is not visible in the shown snippet (it may be used elsewhere).
✓ Persistence & Privilege
always:false (default) and the skill does not request persistent system-wide privileges or modify other skills. Autonomous invocation is allowed (platform default) but this skill does not request elevated persistence.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install clawdbot-jira-skill
  3. After installation, invoke the skill by name or use /clawdbot-jira-skill
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Minor formatting changes in SKILL.md for improved readability. - No changes to functionality or commands.
v1.0.1
Add ability to log hours for issue
v1.0.0
Initial release of the Jira skill for Clawdbot. - Manage Jira issues, transitions, and worklogs using Jira Cloud REST API. - Provides shell commands for searching, creating, updating, and logging work on Jira issues. - Supports issue assignment, status transitions, and commenting from the command line. - Offers commands to view and summarize logged work hours by issue and user. - Requires setup with Jira Cloud credentials and environment variables.
Metadata
Slug clawdbot-jira-skill
Version 1.0.2
License —
All-time Installs 5
Active Installs 4
Total Versions 3
Frequently Asked Questions

What is Jira?

Manage Jira issues, transitions, and worklogs via the Jira Cloud REST API. It is an AI Agent Skill for Claude Code / OpenClaw, with 2825 downloads so far.

How do I install Jira?

Run "/install clawdbot-jira-skill" 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 kyjus25 (@kyjus25); the current version is v1.0.2.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463815 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259802 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200680 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191345 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190333 · by oswalpalash

💬 Comments