jirac SKILL.md skillA
jirac from mulhamna/jira-commands is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mulhamna/jira-commands/jirac@git:20261029.f79e226Pins git:20261029.f79e226 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mulhamna/jira-commands
- Path
clawhub/jirac/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261029.f79e226, committed Oct 29, 2026
- First version recorded
- Apr 23, 2026
- Size
- 10,246 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
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 …
Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/jirac@sha256:65e36a530fdacd61The line at the top of this page pins the label git:20261029.f79e226, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yo67cyzhyhbr56pt)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 23, 2026 and Oct 29, 2026, about one every 47 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261029.f79e226 latest | 2026-10-29 | f79e226 | 10,246 B | A | view · diff |
| git:20260521.f34ad5e | 2026-05-21 | f34ad5e | 10,084 B | A | view · diff |
| git:20260515.291572c | 2026-05-15 | 291572c | 4,945 B | A | view · diff |
| git:20260428.3a23448 | 2026-04-28 | 3a23448 | 4,684 B | A | view · diff |
| git:20260423.0101d8e | 2026-04-23 | 0101d8e | 2,553 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10246 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mulhamna/jira-commands · 54 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yo67cyzhyhbr56pt GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/jirac GET https://markdownregistry.com/api/v1/blob/65e36a530fdacd611ba3266c69ddab04a6735be25a24a86f7ceb4a2752353448
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.