# Send JIRA to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "jira", "name": "JIRA", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/jdrhyne/jira", "canonicalUrl": "https://clawhub.ai/jdrhyne/jira", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/jira", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=jira", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "README.md", "SKILL.md", "_meta.json", "references/commands.md", "references/mcp.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "jira", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T23:18:12.457Z", "expiresAt": "2026-05-06T23:18:12.457Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=jira", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=jira", "contentDisposition": "attachment; filename=\"jira-1.3.3.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "jira" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/jira" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/jira", "downloadUrl": "https://openagent3.xyz/downloads/jira", "agentUrl": "https://openagent3.xyz/skills/jira/agent", "manifestUrl": "https://openagent3.xyz/skills/jira/agent.json", "briefUrl": "https://openagent3.xyz/skills/jira/agent.md" } } ``` ## Documentation ### Jira Natural language interaction with Jira. Supports multiple backends. ### Backend Detection Run this check first to determine which backend to use: 1. Check if jira CLI is available: → Run: which jira → If found: USE CLI BACKEND 2. If no CLI, check for Atlassian MCP: → Look for mcp__atlassian__* tools → If available: USE MCP BACKEND 3. If neither available: → GUIDE USER TO SETUP BackendWhen to UseReferenceCLIjira command availablereferences/commands.mdMCPAtlassian MCP tools availablereferences/mcp.mdNoneNeither availableGuide to install CLI ### Quick Reference (CLI) Skip this section if using MCP backend. IntentCommandView issuejira issue view ISSUE-KEYList my issuesjira issue list -a$(jira me)My in-progressjira issue list -a$(jira me) -s"In Progress"Create issuejira issue create -tType -s"Summary" -b"Description"Move/transitionjira issue move ISSUE-KEY "State"Assign to mejira issue assign ISSUE-KEY $(jira me)Unassignjira issue assign ISSUE-KEY xAdd commentjira issue comment add ISSUE-KEY -b"Comment text"Open in browserjira open ISSUE-KEYCurrent sprintjira sprint list --state activeWho am Ijira me ### Quick Reference (MCP) Skip this section if using CLI backend. IntentMCP ToolSearch issuesmcp__atlassian__searchJiraIssuesUsingJqlView issuemcp__atlassian__getJiraIssueCreate issuemcp__atlassian__createJiraIssueUpdate issuemcp__atlassian__editJiraIssueGet transitionsmcp__atlassian__getTransitionsForJiraIssueTransitionmcp__atlassian__transitionJiraIssueAdd commentmcp__atlassian__addCommentToJiraIssueUser lookupmcp__atlassian__lookupJiraAccountIdList projectsmcp__atlassian__getVisibleJiraProjects See references/mcp.md for full MCP patterns. ### Triggers "create a jira ticket" "show me PROJ-123" "list my tickets" "move ticket to done" "what's in the current sprint" ### Issue Key Detection Issue keys follow the pattern: [A-Z]+-[0-9]+ (e.g., PROJ-123, ABC-1). When a user mentions an issue key in conversation: CLI: jira issue view KEY or jira open KEY MCP: mcp__atlassian__jira_get_issue with the key ### Workflow Creating tickets: Research context if user references code/tickets/PRs Draft ticket content Review with user Create using appropriate backend Updating tickets: Fetch issue details first Check status (careful with in-progress tickets) Show current vs proposed changes Get approval before updating Add comment explaining changes ### Before Any Operation Ask yourself: What's the current state? — Always fetch the issue first. Don't assume status, assignee, or fields are what user thinks they are. Who else is affected? — Check watchers, linked issues, parent epics. A "simple edit" might notify 10 people. Is this reversible? — Transitions may have one-way gates. Some workflows require intermediate states. Description edits have no undo. Do I have the right identifiers? — Issue keys, transition IDs, account IDs. Display names don't work for assignment (MCP). ### NEVER NEVER transition without fetching current status — Workflows may require intermediate states. "To Do" → "Done" might fail silently if "In Progress" is required first. NEVER assign using display name (MCP) — Only account IDs work. Always call lookupJiraAccountId first, or assignment silently fails. NEVER edit description without showing original — Jira has no undo. User must see what they're replacing. NEVER use --no-input without all required fields (CLI) — Fails silently with cryptic errors. Check project's required fields first. NEVER assume transition names are universal — "Done", "Closed", "Complete" vary by project. Always get available transitions first. NEVER bulk-modify without explicit approval — Each ticket change notifies watchers. 10 edits = 10 notification storms. ### Safety Always show the command/tool call before running it Always get approval before modifying tickets Preserve original information when editing Verify updates after applying Always surface authentication issues clearly so the user can resolve them ### No Backend Available If neither CLI nor MCP is available, guide the user: To use Jira, you need one of: 1. **jira CLI** (recommended): https://github.com/ankitpokhrel/jira-cli Install: brew install ankitpokhrel/jira-cli/jira-cli Setup: jira init 2. **Atlassian MCP**: Configure in your MCP settings with Atlassian credentials. ### Deep Dive LOAD reference when: Creating issues with complex fields or multi-line content Building JQL queries beyond simple filters Troubleshooting errors or authentication issues Working with transitions, linking, or sprints Do NOT load reference for: Simple view/list operations (Quick Reference above is sufficient) Basic status checks (jira issue view KEY) Opening issues in browser TaskLoad Reference?View single issueNoList my ticketsNoCreate with descriptionYes — CLI needs /tmp patternTransition issueYes — need transition ID workflowJQL searchYes — for complex queriesLink issuesYes — MCP limitation, need script References: CLI patterns: references/commands.md MCP patterns: references/mcp.md ## Trust - Source: tencent - Verification: Indexed source record - Publisher: jdrhyne - Version: 1.3.3 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T23:18:12.457Z - Expires at: 2026-05-06T23:18:12.457Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/jira) - [Send to Agent page](https://openagent3.xyz/skills/jira/agent) - [JSON manifest](https://openagent3.xyz/skills/jira/agent.json) - [Markdown brief](https://openagent3.xyz/skills/jira/agent.md) - [Download page](https://openagent3.xyz/downloads/jira)