What makes jirac notable?

1.1K downloads. Trust evidence available

How should jirac be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

jirac

Jira issue management skill for OpenClaw using the jirac CLI. Requires the `jirac` binary to be installed and authenticated before use. Use when listing, vie... Skill: jirac Owner: mulhamna Summary: Jira issue management skill for OpenClaw using the jirac CLI. Requires the jirac binary to be installed and authenticated before use. Use when listing, vie... Tags: latest:0.1.8 Version history: v0.1.8 | 2026-05-21T08:26:46.150Z | user feat(plugin): 8 new skills + clawhub SKILL refresh + install docs sync (#266) v0.1.7 | 2026-05-15T15:49:03.299Z | user feat: add Jira standups, sp

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

0.1.8

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 0.1.8release · observed May 21, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17e3cjvcq225cjvf8ng1gev2n85anr6:jirac

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/snapshot"

Documentation

CLAWHUB

45,798 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: jirac
description: Jira issue management skill for OpenClaw using the jirac CLI. Requires the `jirac` binary to be installed and authenticated before use. Use when listing, viewing, creating, updating, transitioning, commenting on, attaching files to, bulk-editing, cloning, deleting, linking, archiving, moving, changing types of Jira issues, logging work, generating standup or sprint summaries, managing sprint lifecycles, browsing fix versions, scanning Jira mention notifications, rendering markdown to ADF, registering jirac-mcp into MCP clients, or running raw Jira REST calls from agent workflows.
metadata: {"openclaw":{"emoji":"🎫","requires":{"bins":["jirac"]},"install":[{"id":"github-releases","kind":"download","label":"Install jirac from GitHub Releases","url":"https://github.com/mulhamna/jira-commands/releases","extract":false}],"homepage":"https://github.com/mulhamna/jira-commands"}}
---

Use `jirac` as the Jira execution surface. The CLI is a single Rust binary that supports Jira Cloud and Jira Data Center, multi-profile auth, runtime custom-field discovery, attachment upload, sprint lifecycle, and an interactive TUI with full mouse support.

## Requirements

- Require the `jirac` binary from the official `jira-commands` release source.
- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.
- Treat Jira credentials, local config (`~/.config/jira/config.toml`), and attachment file paths as sensitive.
- For MCP-based agent setups, additionally require the `jirac-mcp` binary (separate package).

## Pre-flight

1. Run `jirac --version` to confirm the binary is installed.
2. Run `jirac auth status` to confirm credentials are configured and reachable. If not, prompt the user to run `jirac auth login` (or `jirac auth login --profile NAME` for separate accounts).
3. For multi-profile setups, run `jirac auth profiles` and `jirac auth use <name>` to switch the active profile before issuing operations.

## Workflow

1. Prefer direct `jirac` commands over raw Jira REST API (`jirac api`) calls when the CLI already supports the action.
2. Use `jirac issue fields -p PROJ --issue-type Type` when required fields, allowed values, or custom fields are unclear.
3. Use `jirac issue transition <KEY>` without a transition argument to get an interactive picker when the target status is unknown.
4. Use `jirac issue standup` for a concise personal update from assigned work, and `jirac issue sprint-summary -p PROJ` for a project sprint rollup.
5. Use `jirac issue sprints -p PROJ` to see sprint lifecycle states before creating, starting, completing, updating, or deleting a sprint.
6. Use `jirac issue notifications` to scan Jira @mentions from issue descriptions and comments.
7. Use `jirac issue render --input file.md` to preview how Markdown will convert to Jira ADF before sending it as description or comment.
8. Use `jirac tui -p PROJ` for any interactive bulk browse / triage / quick-edit wor

_meta.json

{
  "ownerId": "kn74xexj97nj10bn2azpb21fn585aaw4",
  "slug": "jirac",
  "version": "0.1.8",
  "publishedAt": 1779352006150
}

references/install.md

# Install jirac

Choose the installer that fits your environment. Prefer package managers or verified release archives before using installer scripts.

## Recommended options

### Homebrew (macOS / Linux)

```bash
brew tap mulhamna/tap
brew install jira-commands

# Optional MCP server
brew install jira-mcp
```

### Cargo

```bash
cargo install jira-commands

# Optional MCP server
cargo install jira-mcp
```

### npm

```bash
npm install -g @mulham28/jirac

# Optional MCP server
npm install -g @mulham28/jirac-mcp
```

### GitHub Releases

Download a prebuilt archive or binary from:

- https://github.com/mulhamna/jira-commands/releases

Prefer the packaged archives when available.

Common release artifacts include:

- `jirac-macos-aarch64.tar.gz`
- `jirac-macos-x86_64.tar.gz`
- `jirac-linux-aarch64.tar.gz`
- `jirac-linux-x86_64.tar.gz`
- `jirac-windows-x86_64.zip`

After extracting, place `jirac` on your `PATH`.

## Additional note

Project-provided installer scripts also exist in the repository for users who prefer to inspect them manually, but the recommended ClawHub install paths are Homebrew, Cargo, or a verified GitHub Releases download.

## Verify install

```bash
jirac --version
jirac auth login
jirac auth status
```

references/jql.md

# JQL recipes for jirac

Common JQL fragments to pair with `jirac issue list --jql`, `jirac issue bulk-transition --jql`, `jirac issue bulk-update --jql`, `jirac issue bulk-comment --jql`, and `jirac issue archive --jql`.

## My work

```
assignee = currentUser() AND resolution = Unresolved ORDER BY updated DESC
assignee = currentUser() AND status = "In Progress"
assignee = currentUser() AND sprint in openSprints()
reporter = currentUser() AND created >= -7d ORDER BY created DESC
```

## Project triage

```
project = PROJ AND status = "To Do" AND assignee is EMPTY
project = PROJ AND priority = Highest AND resolution = Unresolved
project = PROJ AND labels = "needs-triage"
project = PROJ AND status = "In Review" AND updated < -2d
```

## Sprint

```
project = PROJ AND sprint = openSprints()
project = PROJ AND sprint = "Sprint 24"
project = PROJ AND sprint in openSprints() AND status != Done
project = PROJ AND sprint in closedSprints() AND resolution = Done AND updated >= -14d
```

## Recency

```
updated >= -7d ORDER BY updated DESC
created >= -7d ORDER BY created DESC
resolutiondate >= -30d AND status = Done
```

## Cleanup / archive candidates

```
project = PROJ AND resolution = Done AND updated < -180d
project = PROJ AND status = "Won't Do" AND updated < -90d
project = PROJ AND status = Done AND fixVersion in releasedVersions() AND updated < -365d
```

## Linking and parents

```
issueLinkType = "blocks" AND project = PROJ
"Epic Link" = PROJ-100
parent = PROJ-50
```

## Combine with bulk flows

```bash
# Bulk-transition every unassigned "To Do" to "In Progress" in PROJ
jirac issue bulk-transition --jql 'project = PROJ AND status = "To Do" AND assignee is EMPTY' --to 'In Progress'

# Bulk-update priority on Low items
jirac issue bulk-update --jql 'project = PROJ AND priority = Low AND resolution = Unresolved' --priority Medium --force

# Bulk-comment on all open sprint items
jirac issue bulk-comment --jql 'project = PROJ AND sprint in openSprints()' --body 'Please post your standup before 10am.'

# Archive done items older than 180 days
jirac issue archive --jql 'project = PROJ AND resolution = Done AND updated < -180d'
```

## Quoting tips

- Wrap the entire JQL in single quotes in bash, use double quotes inside.
- PowerShell: wrap outside in double quotes, escape inner doubles with backtick (`` ` ``).
- Status names with spaces (`"In Progress"`, `"To Do"`) must be quoted in JQL.
- Use `currentUser()`, `openSprints()`, `closedSprints()`, `releasedVersions()`, `unreleasedVersions()` for dynamic values.
- Negate with `!=` or `NOT`. Range with `>=`, `<=`, `BETWEEN`.

skill-card.md

## Description:

Jira issue management skill for OpenClaw using the jirac CLI, covering issue listing, viewing, creation, updates, transitions, comments, attachments, bulk operations, sprint workflows, notifications, Markdown-to-ADF rendering, MCP registration, and raw Jira REST calls.

This skill is ready for commercial/non-commercial use.

## Publisher:

[mulhamna](https://clawhub.ai/user/mulhamna)

### License/Terms of Use:

MIT-0

## Use Case:

Developers, engineers, and project operators use this skill to manage Jira work from an agent through the jirac CLI. It supports routine issue triage, sprint summaries, work logging, comments, attachments, and controlled bulk or workflow-changing actions.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can perform powerful Jira actions, including delete, archive, bulk edit, attachment upload, raw API calls, and MCP registration.

Mitigation: Require explicit review before high-impact actions and preview broad JQL queries with list commands first.

Risk: Installer or command provenance may be difficult for users to verify from the artifact alone.

Mitigation: Install jirac only from a trusted source and prefer a reviewed fixed version when possible.

Risk: Jira credentials and local configuration are sensitive and may grant broad project access.

Mitigation: Authenticate with a least-privilege Jira account and treat credentials, local config, and attachment paths as sensitive.

## Reference(s):

- [Install guide](references/install.md)
- [JQL recipes](references/jql.md)
- [jirac homepage](https://github.com/mulhamna/jira-commands)
- [jirac GitHub Releases](https://github.com/mulhamna/jira-commands/releases)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, configuration, guidance]

**Output Format:** [Markdown with inline shell commands and configuration guidance]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Requires an installed and authenticated jirac binary; optional MCP setup requires jirac-mcp.]

## Skill Version(s):

0.1.8 (source: server release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.