kyjus25

Jira

Business Opsv1.0.2
By kyjus25Updated 2026-05-113 versions · latest released 2026-01-20clawdbot-jira-skill@clawhub_kyjus25/clawdbot-jira-skill
Project ManagementUser Operations#Jira#Rest Api

According to AlphaMoat, as of 2026-09, Jira has 4,002 downloads and 5 stars — ranked #2,557 of 5,078 AI skills overall, and #145 of 297 in Business Ops.

Installs
127
Downloads
4.0K
Stars
5
Overall Rank
#2,557
Top 51% overall · Top 49% in Business Ops
PlatformInstallsDownloadsStarsComments
ClawHub ↗1273.8K5-
SkillHub ↗1254.0K5—

Platforms count differently and update at different times.

What this skill does

This skill queries and manages Jira issues through the Jira Cloud REST API, including status transitions and worklogs. Some commands modify Jira data, such as status, assignee, comments, issue creation, or worklog updates; review the issue key, assignee, comment, status, and hours before running write commands. Requires JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN; obtain explicit approval before each write.

Profile published 2026-10-29

What you can do with it

  • Query and manage Jira issues
  • Transition issue statuses
  • Record or update worklogs

When to use it

  • You need to handle issues through the Jira Cloud API
  • You need to update a status or assignee
  • You need to log work and can review the write details first

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

Check the current status and worklogs for the Jira issue I specify. If a change is needed, show me the issue, change, and hours to be logged, and wait for confirmation before writing.

Monthly Trend

Downloads4.0K
2.6K3.4K4.1K2026-03 · Downloads 2.7K2026-05 · Downloads 3.2K2026-06 · Downloads 3.3K2026-07 · Downloads 3.6K2026-08 · Downloads 3.7K2026-09 · Downloads 4.0K26-0326-09
Stars5
4562026-03 · Stars 52026-05 · Stars 52026-06 · Stars 52026-07 · Stars 52026-08 · Stars 52026-09 · Stars 526-0326-09

The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.

MonthDownloadsMoMStars
2026-094.0K—5
2026-083.7K+4.2%5
2026-073.6K+7.4%5
2026-063.3K+3.7%5
2026-053.2K—5
2026-032.7K—5

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

4.2 KB · ClawHub v1.0.2
---
name: jira
description: Manage Jira issues, transitions, and worklogs via the Jira Cloud REST API.
homepage: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/
metadata:
  {
    "clawdbot":
      {
        "emoji": "🧭",
        "requires":
Show all (155 lines)
          {
            "bins": ["curl", "jq", "bc", "python3"],
            "env": ["JIRA_URL", "JIRA_EMAIL", "JIRA_API_TOKEN"],
            "optional_env": ["JIRA_BOARD"],
          },
      },
  }
---

# 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:
   ```bash
   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**

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

- **Issue link**

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

- **Issue details**

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

- **Update status**

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

- **List transitions**

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

- **Assign issue**

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

- **Assign to yourself**

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

- **Add comment**

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

- **Create issue**

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

- **Log hours**

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

- **My open issues**

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

- **Logged hours by issue (me)**

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

- **Logged hours for a day (everyone)**

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

- **Logged hours for a day (user filter)**

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

- **Logged hours for an issue**
  ```bash
  {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.

Popular in Business Ops

Data month: 2026-09 · Downloads, stars and installs are aggregated monthly from public skill registries (ClawHub, SkillHub). See methodology.