{"id":"52613804-ab5d-4c21-87ca-0890ee26c7c9","entityType":"agent","slug":"clawhub-mulhamna-jirac","name":"jirac","canonicalUrl":"https://www.xpersona.co/agent/clawhub-mulhamna-jirac","canonicalPath":"/agent/clawhub-mulhamna-jirac","generatedAt":"2026-10-11T11:24:23.796Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T09:33:15.181Z","emptyReason":null},"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, 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","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17e3cjvcq225cjvf8ng1gev2n85anr6:jirac","sourceUrl":"https://clawhub.ai/mulhamna/jirac","homepage":"https://clawhub.ai/mulhamna/skills/jirac","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/mulhamna/jirac","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/mulhamna/skills/jirac","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"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..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T09:33:15.181Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T09:33:15.181Z","emptyReason":null},"stars":null,"forks":null,"downloads":1099,"packageName":null,"latestVersion":"0.1.8","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T09:33:15.169Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T09:33:15.181Z","lastCrawledAt":"2026-10-11T09:33:15.169Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T09:33:15.169Z","lastVerifiedAt":null,"highlights":[{"version":"0.1.8","createdAt":"2026-05-21T08:26:46.150Z","changelog":"feat(plugin): 8 new skills + clawhub SKILL refresh + install docs sync (#266)","fileCount":5,"zipByteSize":7178},{"version":"0.1.7","createdAt":"2026-05-15T15:49:03.299Z","changelog":"feat: add Jira standups, sprint summaries, and release lane fixes (#244)","fileCount":3,"zipByteSize":3037},{"version":"0.1.6","createdAt":"2026-04-28T09:19:17.047Z","changelog":"feat: improve TUI sprint, mention, and search flows (#145)","fileCount":3,"zipByteSize":2941},{"version":"0.1.5","createdAt":"2026-04-23T15:11:30.070Z","changelog":"docs(clawhub): prepare jirac publish verification (#84)","fileCount":3,"zipByteSize":2218},{"version":"0.1.3","createdAt":"2026-04-23T12:58:12.766Z","changelog":"update reference/install.md","fileCount":3,"zipByteSize":2180},{"version":"0.1.2","createdAt":"2026-04-23T12:43:58.023Z","changelog":"reference/install.md","fileCount":3,"zipByteSize":2167},{"version":"0.1.1","createdAt":"2026-04-23T12:09:19.285Z","changelog":"Clarify jirac requirements, auth expectations, and safety guidance","fileCount":2,"zipByteSize":1322},{"version":"0.1.0","createdAt":"2026-04-23T11:56:17.238Z","changelog":"Initial ClawHub release","fileCount":2,"zipByteSize":1078}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17e3cjvcq225cjvf8ng1gev2n85anr6:jirac","setupComplexity":"low","setupSteps":["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":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T11:24:23.796Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-mulhamna-jirac/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T09:33:15.181Z","emptyReason":null},"readme":"Skill: jirac\n\nOwner: mulhamna\n\nSummary: 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...\n\nTags: latest:0.1.8\n\nVersion history:\n\nv0.1.8 | 2026-05-21T08:26:46.150Z | user\n\nfeat(plugin): 8 new skills + clawhub SKILL refresh + install docs sync (#266)\n\nv0.1.7 | 2026-05-15T15:49:03.299Z | user\n\nfeat: add Jira standups, sprint summaries, and release lane fixes (#244)\n\nv0.1.6 | 2026-04-28T09:19:17.047Z | user\n\nfeat: improve TUI sprint, mention, and search flows (#145)\n\nv0.1.5 | 2026-04-23T15:11:30.070Z | user\n\ndocs(clawhub): prepare jirac publish verification (#84)\n\nv0.1.3 | 2026-04-23T12:58:12.766Z | user\n\nupdate reference/install.md\n\nv0.1.2 | 2026-04-23T12:43:58.023Z | user\n\nreference/install.md\n\nv0.1.1 | 2026-04-23T12:09:19.285Z | user\n\nClarify jirac requirements, auth expectations, and safety guidance\n\nv0.1.0 | 2026-04-23T11:56:17.238Z | user\n\nInitial ClawHub release\n\nArchive index:\n\nArchive v0.1.8: 5 files, 7178 bytes\n\nFiles: references/install.md (1241b), references/jql.md (2612b), skill-card.md (2401b), SKILL.md (10084b), _meta.json (124b)\n\nFile v0.1.8:SKILL.md\n\n---\nname: jirac\ndescription: 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.\nmetadata: {\"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\"}}\n---\n\nUse `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.\n\n## Requirements\n\n- Require the `jirac` binary from the official `jira-commands` release source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config (`~/.config/jira/config.toml`), and attachment file paths as sensitive.\n- For MCP-based agent setups, additionally require the `jirac-mcp` binary (separate package).\n\n## Pre-flight\n\n1. Run `jirac --version` to confirm the binary is installed.\n2. 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).\n3. For multi-profile setups, run `jirac auth profiles` and `jirac auth use <name>` to switch the active profile before issuing operations.\n\n## Workflow\n\n1. Prefer direct `jirac` commands over raw Jira REST API (`jirac api`) calls when the CLI already supports the action.\n2. Use `jirac issue fields -p PROJ --issue-type Type` when required fields, allowed values, or custom fields are unclear.\n3. Use `jirac issue transition <KEY>` without a transition argument to get an interactive picker when the target status is unknown.\n4. Use `jirac issue standup` for a concise personal update from assigned work, and `jirac issue sprint-summary -p PROJ` for a project sprint rollup.\n5. Use `jirac issue sprints -p PROJ` to see sprint lifecycle states before creating, starting, completing, updating, or deleting a sprint.\n6. Use `jirac issue notifications` to scan Jira @mentions from issue descriptions and comments.\n7. Use `jirac issue render --input file.md` to preview how Markdown will convert to Jira ADF before sending it as description or comment.\n8. Use `jirac tui -p PROJ` for any interactive bulk browse / triage / quick-edit workflow — supports mouse (click rows, tabs, picker options; scroll wheel; drag splitter; click `[?]` / `[🔔]`).\n9. Confirm intent before destructive or high-impact operations: `delete`, `archive`, `bulk-update`, `bulk-transition`, `bulk-comment`, `bulk-create`, `change-type`, `move`, `sprint-delete`, and attachment uploads.\n10. Keep Jira project keys, issue keys, status names, and transition names exact. Use quotes for any name with spaces.\n\n## Common commands\n\n```bash\n# Auth and profiles\njirac auth login                              # interactive, current shell profile\njirac auth login --profile work-cloud         # named profile\njirac auth status\njirac auth profiles\njirac auth use work-cloud\n\n# List, search, summaries\njirac issue list                              # your assigned issues\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue standup                           # daily standup rollup\njirac issue sprint-summary -p PROJ            # current sprint\njirac issue sprint-summary -p PROJ --sprint 'Sprint 24'\njirac issue notifications                     # @mentions scan\njirac issue view PROJ-123\njirac issue view PROJ-123 --versions          # include fix-version block\njirac issue fields -p PROJ --issue-type Bug\njirac issue jql --run                         # interactive JQL builder\n\n# Sprint lifecycle\njirac issue sprints -p PROJ\njirac issue sprint-create -p PROJ --name 'Sprint 25' --goal 'Ship auth v2'\njirac issue sprint-start <SPRINT_ID>\njirac issue sprint-complete <SPRINT_ID>\njirac issue sprint-update <SPRINT_ID> --name 'Sprint 25 (extended)' --goal 'New goal'\njirac issue sprint-delete <SPRINT_ID> --force # destructive\n\n# Versions\njirac issue versions -p PROJ                  # browse + backlog preview\njirac issue versions -p PROJ --version 'v1.2.0'\n\n# Create\njirac issue create -p PROJ                                                          # interactive\njirac issue create -p PROJ -t Bug -s 'login crash' --assignee me\njirac issue create -p PROJ -t Story -s 'auth flow' --sprint 'Sprint 24' --field story_points=5\njirac issue create -p PROJ -t Sub-task -s 'sub-task' --parent PROJ-100\n\n# Update\njirac issue update PROJ-123 --summary 'New title'\njirac issue update PROJ-123 --priority High --assignee me\njirac issue update PROJ-123 --labels backend,api --fix-versions v2.0\njirac issue update PROJ-123 --field story_points=8\n\n# Transition (positional, not --to)\njirac issue transition PROJ-123                # interactive picker\njirac issue transition PROJ-123 'Done'\njirac issue transition PROJ-123 'In Progress'\n\n# Comment / bulk-comment\njirac issue comment list PROJ-123\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue bulk-comment --jql 'project = PROJ AND sprint = openSprints()' --body 'Standup reminder'\njirac issue bulk-comment --keys PROJ-1,PROJ-2,PROJ-3 --body 'Please update'\n\n# Worklog\njirac issue worklog list PROJ-123\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\njirac issue worklog delete PROJ-123 <WORKLOG_ID>\n\n# Attach\njirac issue attach PROJ-123 ./screenshot.png\n\n# Links between issues\njirac issue link list-types\njirac issue link add --link-type Blocks PROJ-123 PROJ-456            # PROJ-123 blocks PROJ-456\njirac issue link add --link-type Relates PROJ-123 PROJ-456\njirac issue link delete <LINK_ID>\n\n# Clone, change-type, move, delete, archive\njirac issue clone PROJ-123                                # same project\njirac issue clone PROJ-123 --project NEWPROJ --summary 'Copy: original'\njirac issue change-type PROJ-123 Bug                      # native Jira move semantics\njirac issue move PROJ-123 NEWPROJ                         # cross-project, native (not clone+delete)\njirac issue delete PROJ-123                               # prompts confirmation\njirac issue delete PROJ-123 --force\njirac issue archive --jql 'project = PROJ AND resolution = Done AND updated < -180d'\n\n# Bulk operations\njirac issue bulk-transition --jql 'project = PROJ AND status = \"To Do\"' --to 'In Progress'\njirac issue bulk-update --jql 'project = PROJ AND assignee = EMPTY' --assignee me\njirac issue bulk-update --jql 'project = PROJ AND priority = Low' --priority High --force\njirac issue bulk-create --manifest issues.json\n\n# Batch (mixed ops from manifest)\njirac issue batch --manifest ops.json\n\n# Render markdown → Jira ADF preview\njirac issue render --input description.md\n\n# Raw REST passthrough (last resort)\njirac api GET /rest/api/3/myself\njirac api POST /rest/api/3/issue --body '{\"fields\":{...}}'\n\n# TUI\njirac tui                                     # uses default project or assigned issues\njirac tui -p PROJ\n\n# MCP server registration (optional)\njirac mcp doctor                              # check prereqs\njirac mcp install                             # interactive client picker\njirac mcp install --client claude-code\njirac mcp install --client cursor\n```\n\n## Bulk-create manifest format\n\n```json\n[\n  {\n    \"project\": \"PROJ\",\n    \"summary\": \"Issue title\",\n    \"type\": \"Task\",\n    \"assignee\": \"user@org.com\",\n    \"priority\": \"High\",\n    \"labels\": [\"backend\"],\n    \"parent\": \"PROJ-100\",\n    \"description\": \"Markdown description\",\n    \"fields\": { \"customfield_10016\": 5 }\n  }\n]\n```\n\n## Batch manifest format\n\n```json\n[\n  { \"op\": \"create\",     \"project\": \"PROJ\", \"summary\": \"New task\", \"type\": \"Task\" },\n  { \"op\": \"update\",     \"key\": \"PROJ-10\",  \"priority\": \"High\", \"assignee\": \"me\" },\n  { \"op\": \"transition\", \"key\": \"PROJ-11\",  \"to\": \"Done\" },\n  { \"op\": \"archive\",    \"key\": \"PROJ-12\" }\n]\n```\n\n## JQL quoting\n\nJQL strings often contain spaces, parentheses, and quotes — wrap the entire `--jql` value in single quotes in bash, then use double quotes inside:\n\n```bash\njirac issue list --jql 'project = PROJ AND status = \"In Progress\" AND assignee = currentUser()'\n```\n\nFor Windows PowerShell, the inverse — wrap in double quotes outside, escape inner doubles with `` ` ``:\n\n```powershell\njirac issue list --jql \"project = PROJ AND status = `\"In Progress`\"\"\n```\n\nSee `references/jql.md` for common JQL recipes.\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear (`jirac issue fields ...`, `jirac issue jql --run`, `jirac issue transition KEY`).\n- Always confirm intent before operations that may change workflow state, bulk-edit, delete, archive, change type, or move issues across projects.\n- Confirm that local files selected for attachment are intended and safe to upload.\n- Prefer explicit project scoping (`-p PROJ`) when working across multiple Jira projects.\n- `jirac issue transition` takes a positional transition name/ID — not `--to`.\n- `jirac issue change-type` and `jirac issue move` use Jira's native move semantics; the issue key is preserved.\n- For agents that need Jira inside an MCP client (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, Zed), install `jirac-mcp` separately, then run `jirac mcp install` for an interactive registration picker.\n\n## References\n\n- Install guide: `references/install.md`\n- JQL recipes: `references/jql.md`\n\nFile v0.1.8:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.8\",\n  \"publishedAt\": 1779352006150\n}\n\nFile v0.1.8:references/install.md\n\n# Install jirac\n\nChoose the installer that fits your environment. Prefer package managers or verified release archives before using installer scripts.\n\n## Recommended options\n\n### Homebrew (macOS / Linux)\n\n```bash\nbrew tap mulhamna/tap\nbrew install jira-commands\n\n# Optional MCP server\nbrew install jira-mcp\n```\n\n### Cargo\n\n```bash\ncargo install jira-commands\n\n# Optional MCP server\ncargo install jira-mcp\n```\n\n### npm\n\n```bash\nnpm install -g @mulham28/jirac\n\n# Optional MCP server\nnpm install -g @mulham28/jirac-mcp\n```\n\n### GitHub Releases\n\nDownload a prebuilt archive or binary from:\n\n- https://github.com/mulhamna/jira-commands/releases\n\nPrefer the packaged archives when available.\n\nCommon release artifacts include:\n\n- `jirac-macos-aarch64.tar.gz`\n- `jirac-macos-x86_64.tar.gz`\n- `jirac-linux-aarch64.tar.gz`\n- `jirac-linux-x86_64.tar.gz`\n- `jirac-windows-x86_64.zip`\n\nAfter extracting, place `jirac` on your `PATH`.\n\n## Additional note\n\nProject-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.\n\n## Verify install\n\n```bash\njirac --version\njirac auth login\njirac auth status\n```\n\nFile v0.1.8:references/jql.md\n\n# JQL recipes for jirac\n\nCommon 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`.\n\n## My work\n\n```\nassignee = currentUser() AND resolution = Unresolved ORDER BY updated DESC\nassignee = currentUser() AND status = \"In Progress\"\nassignee = currentUser() AND sprint in openSprints()\nreporter = currentUser() AND created >= -7d ORDER BY created DESC\n```\n\n## Project triage\n\n```\nproject = PROJ AND status = \"To Do\" AND assignee is EMPTY\nproject = PROJ AND priority = Highest AND resolution = Unresolved\nproject = PROJ AND labels = \"needs-triage\"\nproject = PROJ AND status = \"In Review\" AND updated < -2d\n```\n\n## Sprint\n\n```\nproject = PROJ AND sprint = openSprints()\nproject = PROJ AND sprint = \"Sprint 24\"\nproject = PROJ AND sprint in openSprints() AND status != Done\nproject = PROJ AND sprint in closedSprints() AND resolution = Done AND updated >= -14d\n```\n\n## Recency\n\n```\nupdated >= -7d ORDER BY updated DESC\ncreated >= -7d ORDER BY created DESC\nresolutiondate >= -30d AND status = Done\n```\n\n## Cleanup / archive candidates\n\n```\nproject = PROJ AND resolution = Done AND updated < -180d\nproject = PROJ AND status = \"Won't Do\" AND updated < -90d\nproject = PROJ AND status = Done AND fixVersion in releasedVersions() AND updated < -365d\n```\n\n## Linking and parents\n\n```\nissueLinkType = \"blocks\" AND project = PROJ\n\"Epic Link\" = PROJ-100\nparent = PROJ-50\n```\n\n## Combine with bulk flows\n\n```bash\n# Bulk-transition every unassigned \"To Do\" to \"In Progress\" in PROJ\njirac issue bulk-transition --jql 'project = PROJ AND status = \"To Do\" AND assignee is EMPTY' --to 'In Progress'\n\n# Bulk-update priority on Low items\njirac issue bulk-update --jql 'project = PROJ AND priority = Low AND resolution = Unresolved' --priority Medium --force\n\n# Bulk-comment on all open sprint items\njirac issue bulk-comment --jql 'project = PROJ AND sprint in openSprints()' --body 'Please post your standup before 10am.'\n\n# Archive done items older than 180 days\njirac issue archive --jql 'project = PROJ AND resolution = Done AND updated < -180d'\n```\n\n## Quoting tips\n\n- Wrap the entire JQL in single quotes in bash, use double quotes inside.\n- PowerShell: wrap outside in double quotes, escape inner doubles with backtick (`` ` ``).\n- Status names with spaces (`\"In Progress\"`, `\"To Do\"`) must be quoted in JQL.\n- Use `currentUser()`, `openSprints()`, `closedSprints()`, `releasedVersions()`, `unreleasedVersions()` for dynamic values.\n- Negate with `!=` or `NOT`. Range with `>=`, `<=`, `BETWEEN`.\n\nFile v0.1.8:skill-card.md\n\n## Description:\n\nJira 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.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[mulhamna](https://clawhub.ai/user/mulhamna)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, 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.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can perform powerful Jira actions, including delete, archive, bulk edit, attachment upload, raw API calls, and MCP registration.\n\nMitigation: Require explicit review before high-impact actions and preview broad JQL queries with list commands first.\n\nRisk: Installer or command provenance may be difficult for users to verify from the artifact alone.\n\nMitigation: Install jirac only from a trusted source and prefer a reviewed fixed version when possible.\n\nRisk: Jira credentials and local configuration are sensitive and may grant broad project access.\n\nMitigation: Authenticate with a least-privilege Jira account and treat credentials, local config, and attachment paths as sensitive.\n\n## Reference(s):\n\n- [Install guide](references/install.md)\n- [JQL recipes](references/jql.md)\n- [jirac homepage](https://github.com/mulhamna/jira-commands)\n- [jirac GitHub Releases](https://github.com/mulhamna/jira-commands/releases)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and configuration guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires an installed and authenticated jirac binary; optional MCP setup requires jirac-mcp.]\n\n## Skill Version(s):\n\n0.1.8 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v0.1.7: 3 files, 3037 bytes\n\nFiles: references/install.md (1084b), SKILL.md (4945b), _meta.json (124b)\n\nFile v0.1.7:SKILL.md\n\n---\nname: jirac\ndescription: 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, logging work against Jira issues, or generating standup and sprint summaries from agent workflows.\nmetadata: {\"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\"}}\n---\n\nUse `jirac` as the Jira execution surface.\n\n## Requirements\n\n- Require the `jirac` binary from the official `jira-commands` release source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config, and attachment paths as sensitive.\n\n## Workflow\n\n1. Verify `jirac` is installed by running `jirac --version`.\n2. Verify authentication is already configured before issue operations, for example with `jirac auth status` or a known-good prior login.\n3. Prefer direct `jirac` commands over raw Jira API calls when the CLI already supports the action.\n4. Use `jirac issue fields` when required fields or custom fields are unclear.\n5. Use `jirac issue transition <KEY>` without a transition argument when the target status is not known yet — shows an interactive picker.\n6. Use `jirac issue standup` when the user wants a concise personal update from assigned work, and `jirac issue sprint-summary -p PROJ` for a project sprint rollup.\n7. Confirm intent before destructive or high-impact operations such as delete, bulk edits, transitions, and file attachments.\n\n## Common commands\n\n```bash\n# List and view\njirac issue list\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue standup\njirac issue sprint-summary -p PROJ\njirac issue view PROJ-123\n\n# Create\njirac issue create -p PROJ\njirac issue create -p PROJ -t Bug -s 'login crash' --assignee me\njirac issue create -p PROJ -t Story -s 'auth flow' --sprint 'Sprint 24' --field story_points=5\njirac issue create -p PROJ -t Sub-task -s 'sub-task' --parent PROJ-100\n\n# Update\njirac issue update PROJ-123 --summary 'New title'\njirac issue update PROJ-123 --priority High --assignee me\njirac issue update PROJ-123 --labels backend,api --fix-versions v2.0\njirac issue update PROJ-123 --field story_points=8\n\n# Transition (positional arg, not --to)\njirac issue transition PROJ-123              # interactive picker\njirac issue transition PROJ-123 'Done'\njirac issue transition PROJ-123 'In Progress'\n\n# Comment and worklog\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\n\n# Attach\njirac issue attach PROJ-123 ./screenshot.png\n\n# Clone and delete\njirac issue clone PROJ-123\njirac issue clone PROJ-123 --project NEWPROJ --summary 'Copy: original'\njirac issue delete PROJ-123                  # prompts confirmation\njirac issue delete PROJ-123 --force\n\n# Bulk operations\njirac issue bulk-transition --jql 'project = PROJ AND status = \"To Do\"' --to 'In Progress'\njirac issue bulk-update --jql 'project = PROJ AND assignee = EMPTY' --assignee me\njirac issue bulk-update --jql 'project = PROJ AND priority = Low' --priority High --force\njirac issue bulk-create --manifest issues.json\n\n# Batch (mixed ops from manifest)\njirac issue batch --manifest ops.json\n\n# Fields and JQL\njirac issue fields -p PROJ --issue-type Bug\njirac issue jql --run\n```\n\n## Bulk-create manifest format\n\n```json\n[\n  {\n    \"project\": \"PROJ\",\n    \"summary\": \"Issue title\",\n    \"type\": \"Task\",\n    \"assignee\": \"user@org.com\",\n    \"priority\": \"High\",\n    \"labels\": [\"backend\"],\n    \"parent\": \"PROJ-100\",\n    \"description\": \"Markdown description\",\n    \"fields\": { \"customfield_10016\": 5 }\n  }\n]\n```\n\n## Batch manifest format\n\n```json\n[\n  { \"op\": \"create\",     \"project\": \"PROJ\", \"summary\": \"New task\", \"type\": \"Task\" },\n  { \"op\": \"update\",     \"key\": \"PROJ-10\",  \"priority\": \"High\", \"assignee\": \"me\" },\n  { \"op\": \"transition\", \"key\": \"PROJ-11\",  \"to\": \"Done\" },\n  { \"op\": \"archive\",    \"key\": \"PROJ-12\" }\n]\n```\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear.\n- Confirm intent before operations that may change workflow state, bulk-edit, delete, or overwrite issue content.\n- Confirm that local files selected for attachment are intended and safe to upload.\n- Keep Jira project keys, issue keys, and status names exact.\n- Prefer explicit project scoping in commands when working across multiple Jira projects.\n- `jirac issue transition` takes a positional transition name/ID — not `--to`.\n\n## References\n\n- Install guide: `references/install.md`\n\nFile v0.1.7:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.7\",\n  \"publishedAt\": 1778860143299\n}\n\nFile v0.1.7:references/install.md\n\n# Install jirac\n\nChoose the installer that fits your environment. Prefer package managers or verified release archives before using installer scripts.\n\n## Recommended options\n\n### Homebrew (macOS / Linux)\n\n```bash\nbrew tap mulhamna/tap\nbrew install jira-commands\n\n# Optional MCP server\nbrew install jira-mcp\n```\n\n### Cargo\n\n```bash\ncargo install jira-commands\n```\n\n### GitHub Releases\n\nDownload a prebuilt archive or binary from:\n\n- https://github.com/mulhamna/jira-commands/releases\n\nPrefer the packaged archives when available.\n\nCommon release artifacts include:\n\n- `jirac-macos-aarch64.tar.gz`\n- `jirac-macos-x86_64.tar.gz`\n- `jirac-linux-aarch64.tar.gz`\n- `jirac-linux-x86_64.tar.gz`\n- `jirac-windows-x86_64.zip`\n\nAfter extracting, place `jirac` on your `PATH`.\n\n## Additional note\n\nProject-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.\n\n## Verify install\n\n```bash\njirac --version\njirac auth login\njirac auth status\n```\n\nArchive v0.1.6: 3 files, 2941 bytes\n\nFiles: references/install.md (1084b), SKILL.md (4684b), _meta.json (124b)\n\nFile v0.1.6:SKILL.md\n\n---\nname: jirac\ndescription: 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, or logging work against Jira issues from agent workflows.\nmetadata: {\"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\"}}\n---\n\nUse `jirac` as the Jira execution surface.\n\n## Requirements\n\n- Require the `jirac` binary from the official `jira-commands` release source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config, and attachment paths as sensitive.\n\n## Workflow\n\n1. Verify `jirac` is installed by running `jirac --version`.\n2. Verify authentication is already configured before issue operations, for example with `jirac auth status` or a known-good prior login.\n3. Prefer direct `jirac` commands over raw Jira API calls when the CLI already supports the action.\n4. Use `jirac issue fields` when required fields or custom fields are unclear.\n5. Use `jirac issue transition <KEY>` without a transition argument when the target status is not known yet — shows an interactive picker.\n6. Confirm intent before destructive or high-impact operations such as delete, bulk edits, transitions, and file attachments.\n\n## Common commands\n\n```bash\n# List and view\njirac issue list\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue view PROJ-123\n\n# Create\njirac issue create -p PROJ\njirac issue create -p PROJ -t Bug -s 'login crash' --assignee me\njirac issue create -p PROJ -t Story -s 'auth flow' --sprint 'Sprint 24' --field story_points=5\njirac issue create -p PROJ -t Sub-task -s 'sub-task' --parent PROJ-100\n\n# Update\njirac issue update PROJ-123 --summary 'New title'\njirac issue update PROJ-123 --priority High --assignee me\njirac issue update PROJ-123 --labels backend,api --fix-versions v2.0\njirac issue update PROJ-123 --field story_points=8\n\n# Transition (positional arg, not --to)\njirac issue transition PROJ-123              # interactive picker\njirac issue transition PROJ-123 'Done'\njirac issue transition PROJ-123 'In Progress'\n\n# Comment and worklog\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\n\n# Attach\njirac issue attach PROJ-123 ./screenshot.png\n\n# Clone and delete\njirac issue clone PROJ-123\njirac issue clone PROJ-123 --project NEWPROJ --summary 'Copy: original'\njirac issue delete PROJ-123                  # prompts confirmation\njirac issue delete PROJ-123 --force\n\n# Bulk operations\njirac issue bulk-transition --jql 'project = PROJ AND status = \"To Do\"' --to 'In Progress'\njirac issue bulk-update --jql 'project = PROJ AND assignee = EMPTY' --assignee me\njirac issue bulk-update --jql 'project = PROJ AND priority = Low' --priority High --force\njirac issue bulk-create --manifest issues.json\n\n# Batch (mixed ops from manifest)\njirac issue batch --manifest ops.json\n\n# Fields and JQL\njirac issue fields -p PROJ --issue-type Bug\njirac issue jql --run\n```\n\n## Bulk-create manifest format\n\n```json\n[\n  {\n    \"project\": \"PROJ\",\n    \"summary\": \"Issue title\",\n    \"type\": \"Task\",\n    \"assignee\": \"user@org.com\",\n    \"priority\": \"High\",\n    \"labels\": [\"backend\"],\n    \"parent\": \"PROJ-100\",\n    \"description\": \"Markdown description\",\n    \"fields\": { \"customfield_10016\": 5 }\n  }\n]\n```\n\n## Batch manifest format\n\n```json\n[\n  { \"op\": \"create\",     \"project\": \"PROJ\", \"summary\": \"New task\", \"type\": \"Task\" },\n  { \"op\": \"update\",     \"key\": \"PROJ-10\",  \"priority\": \"High\", \"assignee\": \"me\" },\n  { \"op\": \"transition\", \"key\": \"PROJ-11\",  \"to\": \"Done\" },\n  { \"op\": \"archive\",    \"key\": \"PROJ-12\" }\n]\n```\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear.\n- Confirm intent before operations that may change workflow state, bulk-edit, delete, or overwrite issue content.\n- Confirm that local files selected for attachment are intended and safe to upload.\n- Keep Jira project keys, issue keys, and status names exact.\n- Prefer explicit project scoping in commands when working across multiple Jira projects.\n- `jirac issue transition` takes a positional transition name/ID — not `--to`.\n\n## References\n\n- Install guide: `references/install.md`\n\nFile v0.1.6:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.6\",\n  \"publishedAt\": 1777367957047\n}\n\nFile v0.1.6:references/install.md\n\n# Install jirac\n\nChoose the installer that fits your environment. Prefer package managers or verified release archives before using installer scripts.\n\n## Recommended options\n\n### Homebrew (macOS / Linux)\n\n```bash\nbrew tap mulhamna/tap\nbrew install jira-commands\n\n# Optional MCP server\nbrew install jira-mcp\n```\n\n### Cargo\n\n```bash\ncargo install jira-commands\n```\n\n### GitHub Releases\n\nDownload a prebuilt archive or binary from:\n\n- https://github.com/mulhamna/jira-commands/releases\n\nPrefer the packaged archives when available.\n\nCommon release artifacts include:\n\n- `jirac-macos-aarch64.tar.gz`\n- `jirac-macos-x86_64.tar.gz`\n- `jirac-linux-aarch64.tar.gz`\n- `jirac-linux-x86_64.tar.gz`\n- `jirac-windows-x86_64.zip`\n\nAfter extracting, place `jirac` on your `PATH`.\n\n## Additional note\n\nProject-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.\n\n## Verify install\n\n```bash\njirac --version\njirac auth login\njirac auth status\n```\n\nArchive v0.1.5: 3 files, 2218 bytes\n\nFiles: references/install.md (1039b), SKILL.md (2553b), _meta.json (124b)\n\nFile v0.1.5:SKILL.md\n\n---\nname: jirac\ndescription: 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, or logging work against Jira issues from agent workflows.\nmetadata: {\"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\"}}\n---\n\nUse `jirac` as the Jira execution surface.\n\n## Requirements\n\n- Require the `jirac` binary from the official `jira-commands` release source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config, and attachment paths as sensitive.\n\n## Workflow\n\n1. Verify `jirac` is installed by running `jirac --version`.\n2. Verify authentication is already configured before issue operations, for example with `jirac auth status` or a known-good prior login.\n3. Prefer direct `jirac` commands over raw Jira API calls when the CLI already supports the action.\n4. Use `jirac issue fields` when required fields or custom fields are unclear.\n5. Use `jirac issue transition <KEY>` without `--to` when the target status is not known yet.\n6. Confirm intent before destructive or high-impact operations such as delete, bulk edits, transitions, and file attachments.\n\n## Common commands\n\n```bash\njirac issue list\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue view PROJ-123\njirac issue create -p PROJ\njirac issue update PROJ-123 --summary 'New title'\njirac issue transition PROJ-123 --to 'Done'\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\njirac issue attach PROJ-123 ./screenshot.png\n```\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear.\n- Confirm intent before operations that may change workflow state, bulk-edit, delete, or overwrite issue content.\n- Confirm that local files selected for attachment are intended and safe to upload.\n- Keep Jira project keys, issue keys, and status names exact.\n- Prefer explicit project scoping in commands when working across multiple Jira projects.\n\n## References\n\n- Install guide: `references/install.md`\n\nFile v0.1.5:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.5\",\n  \"publishedAt\": 1776957090070\n}\n\nFile v0.1.5:references/install.md\n\n# Install jirac\n\nChoose the installer that fits your environment. Prefer package managers or verified release archives before using installer scripts.\n\n## Recommended options\n\n### Homebrew (macOS / Linux)\n\n```bash\nbrew tap mulhamna/tap\nbrew install jira-commands\n```\n\n### Cargo\n\n```bash\ncargo install jira-commands\n```\n\n### GitHub Releases\n\nDownload a prebuilt archive or binary from:\n\n- https://github.com/mulhamna/jira-commands/releases\n\nPrefer the packaged archives when available.\n\nCommon release artifacts include:\n\n- `jirac-macos-aarch64.tar.gz`\n- `jirac-macos-x86_64.tar.gz`\n- `jirac-linux-aarch64.tar.gz`\n- `jirac-linux-x86_64.tar.gz`\n- `jirac-windows-x86_64.zip`\n\nAfter extracting, place `jirac` on your `PATH`.\n\n## Additional note\n\nProject-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.\n\n## Verify install\n\n```bash\njirac --version\njirac auth login\njirac auth status\n```\n\nArchive v0.1.3: 3 files, 2180 bytes\n\nFiles: references/install.md (1039b), SKILL.md (2463b), _meta.json (124b)\n\nFile v0.1.3:SKILL.md\n\n---\nname: jirac\ndescription: 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, or logging work against Jira issues from agent workflows.\nmetadata: {\"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\"}}\n---\n\nUse `jirac` as the Jira execution surface.\n\n## Requirements\n\n- Require the `jirac` binary from the official `jira-commands` release source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config, and attachment paths as sensitive.\n\n## Workflow\n\n1. Verify `jirac` is installed by running `jirac --version`.\n2. Verify authentication is already configured before issue operations, for example with `jirac auth status` or a known-good prior login.\n3. Prefer direct `jirac` commands over raw Jira API calls when the CLI already supports the action.\n4. Use `jirac issue fields` when required fields or custom fields are unclear.\n5. Use `jirac issue transition <KEY>` without `--to` when the target status is not known yet.\n6. Confirm intent before destructive or high-impact operations such as delete, bulk edits, transitions, and file attachments.\n\n## Common commands\n\n```bash\njirac issue list\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue view PROJ-123\njirac issue create -p PROJ\njirac issue update PROJ-123 --summary 'New title'\njirac issue transition PROJ-123 --to 'Done'\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\njirac issue attach PROJ-123 ./screenshot.png\n```\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear.\n- Confirm intent before operations that may change workflow state, bulk-edit, delete, or overwrite issue content.\n- Confirm that local files selected for attachment are intended and safe to upload.\n- Keep Jira project keys, issue keys, and status names exact.\n\n## References\n\n- Install guide: `references/install.md`\n\nFile v0.1.3:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.3\",\n  \"publishedAt\": 1776949092766\n}\n\nFile v0.1.3:references/install.md\n\n# Install jirac\n\nChoose the installer that fits your environment. Prefer package managers or verified release archives before using installer scripts.\n\n## Recommended options\n\n### Homebrew (macOS / Linux)\n\n```bash\nbrew tap mulhamna/tap\nbrew install jira-commands\n```\n\n### Cargo\n\n```bash\ncargo install jira-commands\n```\n\n### GitHub Releases\n\nDownload a prebuilt archive or binary from:\n\n- https://github.com/mulhamna/jira-commands/releases\n\nPrefer the packaged archives when available.\n\nCommon release artifacts include:\n\n- `jirac-macos-aarch64.tar.gz`\n- `jirac-macos-x86_64.tar.gz`\n- `jirac-linux-aarch64.tar.gz`\n- `jirac-linux-x86_64.tar.gz`\n- `jirac-windows-x86_64.zip`\n\nAfter extracting, place `jirac` on your `PATH`.\n\n## Additional note\n\nProject-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.\n\n## Verify install\n\n```bash\njirac --version\njirac auth login\njirac auth status\n```\n\nArchive v0.1.2: 3 files, 2167 bytes\n\nFiles: references/install.md (1051b), SKILL.md (2463b), _meta.json (124b)\n\nFile v0.1.2:SKILL.md\n\n---\nname: jirac\ndescription: 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, or logging work against Jira issues from agent workflows.\nmetadata: {\"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\"}}\n---\n\nUse `jirac` as the Jira execution surface.\n\n## Requirements\n\n- Require the `jirac` binary from the official `jira-commands` release source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config, and attachment paths as sensitive.\n\n## Workflow\n\n1. Verify `jirac` is installed by running `jirac --version`.\n2. Verify authentication is already configured before issue operations, for example with `jirac auth status` or a known-good prior login.\n3. Prefer direct `jirac` commands over raw Jira API calls when the CLI already supports the action.\n4. Use `jirac issue fields` when required fields or custom fields are unclear.\n5. Use `jirac issue transition <KEY>` without `--to` when the target status is not known yet.\n6. Confirm intent before destructive or high-impact operations such as delete, bulk edits, transitions, and file attachments.\n\n## Common commands\n\n```bash\njirac issue list\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue view PROJ-123\njirac issue create -p PROJ\njirac issue update PROJ-123 --summary 'New title'\njirac issue transition PROJ-123 --to 'Done'\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\njirac issue attach PROJ-123 ./screenshot.png\n```\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear.\n- Confirm intent before operations that may change workflow state, bulk-edit, delete, or overwrite issue content.\n- Confirm that local files selected for attachment are intended and safe to upload.\n- Keep Jira project keys, issue keys, and status names exact.\n\n## References\n\n- Install guide: `references/install.md`\n\nFile v0.1.2:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.2\",\n  \"publishedAt\": 1776948238023\n}\n\nFile v0.1.2:references/install.md\n\n# Install jirac\n\nChoose the installer that fits your environment.\n\n## Homebrew (macOS / Linux)\n\n```bash\nbrew tap mulhamna/tap\nbrew install jira-commands\n```\n\n## Cargo\n\n```bash\ncargo install jira-commands\n```\n\n## GitHub Releases\n\nDownload a prebuilt archive or binary from:\n\n- https://github.com/mulhamna/jira-commands/releases\n\nPrefer the packaged archives when available.\n\nCommon release artifacts include:\n\n- `jirac-macos-aarch64.tar.gz`\n- `jirac-macos-x86_64.tar.gz`\n- `jirac-linux-aarch64.tar.gz`\n- `jirac-linux-x86_64.tar.gz`\n- `jirac-windows-x86_64.zip`\n\nAfter extracting, place `jirac` on your `PATH`.\n\n## Windows install script\n\n```powershell\npowershell -ExecutionPolicy Bypass -Command \"& ([scriptblock]::Create((Invoke-WebRequest 'https://raw.githubusercontent.com/mulhamna/jira-commands/main/install.ps1').Content))\"\n```\n\n## macOS / Linux install script\n\n```bash\ncurl -sSL https://raw.githubusercontent.com/mulhamna/jira-commands/main/install.sh | bash\n```\n\n## Verify install\n\n```bash\njirac --version\njirac auth login\njirac auth status\n```\n\nArchive v0.1.1: 2 files, 1322 bytes\n\nFiles: SKILL.md (2092b), _meta.json (124b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: jirac\ndescription: 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, or logging work against Jira issues from agent workflows.\n---\n\nUse `jirac` as the Jira execution surface.\n\n## Requirements\n\n- Require the `jirac` binary from a trusted installation source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config, and attachment paths as sensitive.\n\n## Workflow\n\n1. Verify `jirac` is installed by running `jirac --version`.\n2. Verify authentication is already configured before issue operations, for example with `jirac auth status` or a known-good prior login.\n3. Prefer direct `jirac` commands over raw Jira API calls when the CLI already supports the action.\n4. Use `jirac issue fields` when required fields or custom fields are unclear.\n5. Use `jirac issue transition <KEY>` without `--to` when the target status is not known yet.\n6. Confirm intent before destructive or high-impact operations such as delete, bulk edits, transitions, and file attachments.\n\n## Common commands\n\n```bash\njirac issue list\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue view PROJ-123\njirac issue create -p PROJ\njirac issue update PROJ-123 --summary 'New title'\njirac issue transition PROJ-123 --to 'Done'\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\njirac issue attach PROJ-123 ./screenshot.png\n```\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear.\n- Confirm intent before operations that may change workflow state, bulk-edit, delete, or overwrite issue content.\n- Confirm that local files selected for attachment are intended and safe to upload.\n- Keep Jira project keys, issue keys, and status names exact.\n\nFile v0.1.1:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.1\",\n  \"publishedAt\": 1776946159285\n}\n\nArchive v0.1.0: 2 files, 1078 bytes\n\nFiles: SKILL.md (1446b), _meta.json (124b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: jirac\ndescription: Jira issue management skill for OpenClaw using the jirac CLI. Use when listing, viewing, creating, updating, transitioning, commenting on, attaching files to, or logging work against Jira issues from agent workflows.\n---\n\nUse `jirac` as the Jira execution surface.\n\n## Workflow\n\n1. Verify `jirac` is installed by running `jirac --version`.\n2. Prefer direct `jirac` commands over raw Jira API calls when the CLI already supports the action.\n3. Use `jirac issue fields` when required fields or custom fields are unclear.\n4. Use `jirac issue transition <KEY>` without `--to` when the target status is not known yet.\n5. Be explicit before destructive or high-impact operations.\n\n## Common commands\n\n```bash\njirac issue list\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue view PROJ-123\njirac issue create -p PROJ\njirac issue update PROJ-123 --summary 'New title'\njirac issue transition PROJ-123 --to 'Done'\njirac issue comment add PROJ-123 --body 'QA verified in staging'\njirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'\njirac issue attach PROJ-123 ./screenshot.png\n```\n\n## Guidance\n\n- Prefer interactive or metadata-assisted flows when field requirements are unclear.\n- Confirm intent before operations that may change workflow state, bulk-edit, or overwrite issue content.\n- Keep Jira project keys, issue keys, and status names exact.\n\nFile v0.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.0\",\n  \"publishedAt\": 1776945377238\n}","readmeExcerpt":"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","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"# Auth and profiles\njirac auth login                              # interactive, current shell profile\njirac auth login --profile work-cloud         # named profile\njirac auth status\njirac auth profiles\njirac auth use work-cloud\n\n# List, search, summaries\njirac issue list                              # your assigned issues\njirac issue list -p PROJ\njirac issue list --jql 'project = PROJ AND status = \"In Progress\"'\njirac issue standup                           # daily standup rollup\njirac issue sprint-summary -p PROJ            # current sprint\njirac issue sprint-summary -p PROJ --sprint 'Sprint 24'\njirac issue notifications                     # @mentions scan\njirac issue view PROJ-123\njirac issue view PROJ-123 --versions          # include fix-version block\njirac issue fields -p PROJ --issue-type Bug\njirac issue jql --run                         # interactive JQL builder\n\n# Sprint lifecycle\njirac issue sprints -p PROJ\njirac issue sprint-create -p PROJ --name 'Sprint 25' --goal 'Ship auth v2'\njirac issue sprint-start <SPRINT_ID>\njirac issue sprint-complete <SPRINT_ID>\njirac issue sprint-update <SPRINT_ID> --name 'Sprint 25 (extended)' --goal 'New goal'\njirac issue sprint-delete <SPRINT_ID> --force # destructive\n\n# Versions\njirac issue versions -p PROJ                  # browse + backlog preview\njirac issue versions -p PROJ --version 'v1.2.0'\n\n# Create\njirac issue create -p PROJ                                                          # interactive\njirac issue create -p PROJ -t Bug -s 'login crash' --assignee me\njirac issue create -p PROJ -t Story -s 'auth flow' --sprint 'Sprint 24' --field story_points=5\njirac issue create -p PROJ -t Sub-task -s 'sub-task' --parent PROJ-100\n\n# Update\njirac issue update PROJ-123 --summary 'New title'\njirac issue update PROJ-123 --priority High --assignee me\njirac issue update PROJ-123 --labels backend,api --fix-versions v2.0\njirac issue update PROJ-123 --field story_points=8\n\n# Transition (positional, not --to)\njirac issue transition "},{"language":"json","snippet":"[\n  {\n    \"project\": \"PROJ\",\n    \"summary\": \"Issue title\",\n    \"type\": \"Task\",\n    \"assignee\": \"user@org.com\",\n    \"priority\": \"High\",\n    \"labels\": [\"backend\"],\n    \"parent\": \"PROJ-100\",\n    \"description\": \"Markdown description\",\n    \"fields\": { \"customfield_10016\": 5 }\n  }\n]"},{"language":"json","snippet":"[\n  { \"op\": \"create\",     \"project\": \"PROJ\", \"summary\": \"New task\", \"type\": \"Task\" },\n  { \"op\": \"update\",     \"key\": \"PROJ-10\",  \"priority\": \"High\", \"assignee\": \"me\" },\n  { \"op\": \"transition\", \"key\": \"PROJ-11\",  \"to\": \"Done\" },\n  { \"op\": \"archive\",    \"key\": \"PROJ-12\" }\n]"},{"language":"bash","snippet":"jirac issue list --jql 'project = PROJ AND status = \"In Progress\" AND assignee = currentUser()'"},{"language":"powershell","snippet":"jirac issue list --jql \"project = PROJ AND status = `\"In Progress`\"\""},{"language":"bash","snippet":"brew tap mulhamna/tap\nbrew install jira-commands\n\n# Optional MCP server\nbrew install jira-mcp"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: jirac\ndescription: 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.\nmetadata: {\"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\"}}\n---\n\nUse `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.\n\n## Requirements\n\n- Require the `jirac` binary from the official `jira-commands` release source.\n- Require Jira authentication to be configured before use, typically via `jirac auth login` in the target environment.\n- Treat Jira credentials, local config (`~/.config/jira/config.toml`), and attachment file paths as sensitive.\n- For MCP-based agent setups, additionally require the `jirac-mcp` binary (separate package).\n\n## Pre-flight\n\n1. Run `jirac --version` to confirm the binary is installed.\n2. 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).\n3. For multi-profile setups, run `jirac auth profiles` and `jirac auth use <name>` to switch the active profile before issuing operations.\n\n## Workflow\n\n1. Prefer direct `jirac` commands over raw Jira REST API (`jirac api`) calls when the CLI already supports the action.\n2. Use `jirac issue fields -p PROJ --issue-type Type` when required fields, allowed values, or custom fields are unclear.\n3. Use `jirac issue transition <KEY>` without a transition argument to get an interactive picker when the target status is unknown.\n4. Use `jirac issue standup` for a concise personal update from assigned work, and `jirac issue sprint-summary -p PROJ` for a project sprint rollup.\n5. Use `jirac issue sprints -p PROJ` to see sprint lifecycle states before creating, starting, completing, updating, or deleting a sprint.\n6. Use `jirac issue notifications` to scan Jira @mentions from issue descriptions and comments.\n7. Use `jirac issue render --input file.md` to preview how Markdown will convert to Jira ADF before sending it as description or comment.\n8. Use `jirac tui -p PROJ` for any interactive bulk browse / triage / quick-edit wor"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn74xexj97nj10bn2azpb21fn585aaw4\",\n  \"slug\": \"jirac\",\n  \"version\": \"0.1.8\",\n  \"publishedAt\": 1779352006150\n}"},{"path":"references/install.md","content":"# Install jirac\n\nChoose the installer that fits your environment. Prefer package managers or verified release archives before using installer scripts.\n\n## Recommended options\n\n### Homebrew (macOS / Linux)\n\n```bash\nbrew tap mulhamna/tap\nbrew install jira-commands\n\n# Optional MCP server\nbrew install jira-mcp\n```\n\n### Cargo\n\n```bash\ncargo install jira-commands\n\n# Optional MCP server\ncargo install jira-mcp\n```\n\n### npm\n\n```bash\nnpm install -g @mulham28/jirac\n\n# Optional MCP server\nnpm install -g @mulham28/jirac-mcp\n```\n\n### GitHub Releases\n\nDownload a prebuilt archive or binary from:\n\n- https://github.com/mulhamna/jira-commands/releases\n\nPrefer the packaged archives when available.\n\nCommon release artifacts include:\n\n- `jirac-macos-aarch64.tar.gz`\n- `jirac-macos-x86_64.tar.gz`\n- `jirac-linux-aarch64.tar.gz`\n- `jirac-linux-x86_64.tar.gz`\n- `jirac-windows-x86_64.zip`\n\nAfter extracting, place `jirac` on your `PATH`.\n\n## Additional note\n\nProject-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.\n\n## Verify install\n\n```bash\njirac --version\njirac auth login\njirac auth status\n```"},{"path":"references/jql.md","content":"# JQL recipes for jirac\n\nCommon 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`.\n\n## My work\n\n```\nassignee = currentUser() AND resolution = Unresolved ORDER BY updated DESC\nassignee = currentUser() AND status = \"In Progress\"\nassignee = currentUser() AND sprint in openSprints()\nreporter = currentUser() AND created >= -7d ORDER BY created DESC\n```\n\n## Project triage\n\n```\nproject = PROJ AND status = \"To Do\" AND assignee is EMPTY\nproject = PROJ AND priority = Highest AND resolution = Unresolved\nproject = PROJ AND labels = \"needs-triage\"\nproject = PROJ AND status = \"In Review\" AND updated < -2d\n```\n\n## Sprint\n\n```\nproject = PROJ AND sprint = openSprints()\nproject = PROJ AND sprint = \"Sprint 24\"\nproject = PROJ AND sprint in openSprints() AND status != Done\nproject = PROJ AND sprint in closedSprints() AND resolution = Done AND updated >= -14d\n```\n\n## Recency\n\n```\nupdated >= -7d ORDER BY updated DESC\ncreated >= -7d ORDER BY created DESC\nresolutiondate >= -30d AND status = Done\n```\n\n## Cleanup / archive candidates\n\n```\nproject = PROJ AND resolution = Done AND updated < -180d\nproject = PROJ AND status = \"Won't Do\" AND updated < -90d\nproject = PROJ AND status = Done AND fixVersion in releasedVersions() AND updated < -365d\n```\n\n## Linking and parents\n\n```\nissueLinkType = \"blocks\" AND project = PROJ\n\"Epic Link\" = PROJ-100\nparent = PROJ-50\n```\n\n## Combine with bulk flows\n\n```bash\n# Bulk-transition every unassigned \"To Do\" to \"In Progress\" in PROJ\njirac issue bulk-transition --jql 'project = PROJ AND status = \"To Do\" AND assignee is EMPTY' --to 'In Progress'\n\n# Bulk-update priority on Low items\njirac issue bulk-update --jql 'project = PROJ AND priority = Low AND resolution = Unresolved' --priority Medium --force\n\n# Bulk-comment on all open sprint items\njirac issue bulk-comment --jql 'project = PROJ AND sprint in openSprints()' --body 'Please post your standup before 10am.'\n\n# Archive done items older than 180 days\njirac issue archive --jql 'project = PROJ AND resolution = Done AND updated < -180d'\n```\n\n## Quoting tips\n\n- Wrap the entire JQL in single quotes in bash, use double quotes inside.\n- PowerShell: wrap outside in double quotes, escape inner doubles with backtick (`` ` ``).\n- Status names with spaces (`\"In Progress\"`, `\"To Do\"`) must be quoted in JQL.\n- Use `currentUser()`, `openSprints()`, `closedSprints()`, `releasedVersions()`, `unreleasedVersions()` for dynamic values.\n- Negate with `!=` or `NOT`. Range with `>=`, `<=`, `BETWEEN`."},{"path":"skill-card.md","content":"## Description:\n\nJira 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.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[mulhamna](https://clawhub.ai/user/mulhamna)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, 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.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can perform powerful Jira actions, including delete, archive, bulk edit, attachment upload, raw API calls, and MCP registration.\n\nMitigation: Require explicit review before high-impact actions and preview broad JQL queries with list commands first.\n\nRisk: Installer or command provenance may be difficult for users to verify from the artifact alone.\n\nMitigation: Install jirac only from a trusted source and prefer a reviewed fixed version when possible.\n\nRisk: Jira credentials and local configuration are sensitive and may grant broad project access.\n\nMitigation: Authenticate with a least-privilege Jira account and treat credentials, local config, and attachment paths as sensitive.\n\n## Reference(s):\n\n- [Install guide](references/install.md)\n- [JQL recipes](references/jql.md)\n- [jirac homepage](https://github.com/mulhamna/jira-commands)\n- [jirac GitHub Releases](https://github.com/mulhamna/jira-commands/releases)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and configuration guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires an installed and authenticated jirac binary; optional MCP setup requires jirac-mcp.]\n\n## Skill Version(s):\n\n0.1.8 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers 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."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"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","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1394,"uniquenessScore":48,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T09:33:15.181Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T09:33:15.181Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T11:24:23.796Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}