{
  "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": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/jira",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=jira",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "README.md",
      "SKILL.md",
      "_meta.json",
      "references/commands.md",
      "references/mcp.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "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."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "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."
        },
        {
          "label": "Upgrade existing",
          "body": "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."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "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."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/jira",
    "agentPageUrl": "https://openagent3.xyz/skills/jira/agent",
    "manifestUrl": "https://openagent3.xyz/skills/jira/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/jira/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "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."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "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."
      },
      {
        "label": "Upgrade existing",
        "body": "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."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Jira",
        "body": "Natural language interaction with Jira. Supports multiple backends."
      },
      {
        "title": "Backend Detection",
        "body": "Run this check first to determine which backend to use:\n\n1. Check if jira CLI is available:\n   → Run: which jira\n   → If found: USE CLI BACKEND\n\n2. If no CLI, check for Atlassian MCP:\n   → Look for mcp__atlassian__* tools\n   → If available: USE MCP BACKEND\n\n3. If neither available:\n   → GUIDE USER TO SETUP\n\nBackendWhen to UseReferenceCLIjira command availablereferences/commands.mdMCPAtlassian MCP tools availablereferences/mcp.mdNoneNeither availableGuide to install CLI"
      },
      {
        "title": "Quick Reference (CLI)",
        "body": "Skip this section if using MCP backend.\n\nIntentCommandView 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"
      },
      {
        "title": "Quick Reference (MCP)",
        "body": "Skip this section if using CLI backend.\n\nIntentMCP 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\n\nSee references/mcp.md for full MCP patterns."
      },
      {
        "title": "Triggers",
        "body": "\"create a jira ticket\"\n\"show me PROJ-123\"\n\"list my tickets\"\n\"move ticket to done\"\n\"what's in the current sprint\""
      },
      {
        "title": "Issue Key Detection",
        "body": "Issue keys follow the pattern: [A-Z]+-[0-9]+ (e.g., PROJ-123, ABC-1).\n\nWhen a user mentions an issue key in conversation:\n\nCLI: jira issue view KEY or jira open KEY\nMCP: mcp__atlassian__jira_get_issue with the key"
      },
      {
        "title": "Workflow",
        "body": "Creating tickets:\n\nResearch context if user references code/tickets/PRs\nDraft ticket content\nReview with user\nCreate using appropriate backend\n\nUpdating tickets:\n\nFetch issue details first\nCheck status (careful with in-progress tickets)\nShow current vs proposed changes\nGet approval before updating\nAdd comment explaining changes"
      },
      {
        "title": "Before Any Operation",
        "body": "Ask yourself:\n\nWhat's the current state? — Always fetch the issue first. Don't assume status, assignee, or fields are what user thinks they are.\n\n\nWho else is affected? — Check watchers, linked issues, parent epics. A \"simple edit\" might notify 10 people.\n\n\nIs this reversible? — Transitions may have one-way gates. Some workflows require intermediate states. Description edits have no undo.\n\n\nDo I have the right identifiers? — Issue keys, transition IDs, account IDs. Display names don't work for assignment (MCP)."
      },
      {
        "title": "NEVER",
        "body": "NEVER transition without fetching current status — Workflows may require intermediate states. \"To Do\" → \"Done\" might fail silently if \"In Progress\" is required first.\n\n\nNEVER assign using display name (MCP) — Only account IDs work. Always call lookupJiraAccountId first, or assignment silently fails.\n\n\nNEVER edit description without showing original — Jira has no undo. User must see what they're replacing.\n\n\nNEVER use --no-input without all required fields (CLI) — Fails silently with cryptic errors. Check project's required fields first.\n\n\nNEVER assume transition names are universal — \"Done\", \"Closed\", \"Complete\" vary by project. Always get available transitions first.\n\n\nNEVER bulk-modify without explicit approval — Each ticket change notifies watchers. 10 edits = 10 notification storms."
      },
      {
        "title": "Safety",
        "body": "Always show the command/tool call before running it\nAlways get approval before modifying tickets\nPreserve original information when editing\nVerify updates after applying\nAlways surface authentication issues clearly so the user can resolve them"
      },
      {
        "title": "No Backend Available",
        "body": "If neither CLI nor MCP is available, guide the user:\n\nTo use Jira, you need one of:\n\n1. **jira CLI** (recommended):\n   https://github.com/ankitpokhrel/jira-cli\n\n   Install: brew install ankitpokhrel/jira-cli/jira-cli\n   Setup:   jira init\n\n2. **Atlassian MCP**:\n   Configure in your MCP settings with Atlassian credentials."
      },
      {
        "title": "Deep Dive",
        "body": "LOAD reference when:\n\nCreating issues with complex fields or multi-line content\nBuilding JQL queries beyond simple filters\nTroubleshooting errors or authentication issues\nWorking with transitions, linking, or sprints\n\nDo NOT load reference for:\n\nSimple view/list operations (Quick Reference above is sufficient)\nBasic status checks (jira issue view KEY)\nOpening issues in browser\n\nTaskLoad 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\n\nReferences:\n\nCLI patterns: references/commands.md\nMCP patterns: references/mcp.md"
      }
    ],
    "body": "Jira\n\nNatural language interaction with Jira. Supports multiple backends.\n\nBackend Detection\n\nRun this check first to determine which backend to use:\n\n1. Check if jira CLI is available:\n   → Run: which jira\n   → If found: USE CLI BACKEND\n\n2. If no CLI, check for Atlassian MCP:\n   → Look for mcp__atlassian__* tools\n   → If available: USE MCP BACKEND\n\n3. If neither available:\n   → GUIDE USER TO SETUP\n\nBackend\tWhen to Use\tReference\nCLI\tjira command available\treferences/commands.md\nMCP\tAtlassian MCP tools available\treferences/mcp.md\nNone\tNeither available\tGuide to install CLI\nQuick Reference (CLI)\n\nSkip this section if using MCP backend.\n\nIntent\tCommand\nView issue\tjira issue view ISSUE-KEY\nList my issues\tjira issue list -a$(jira me)\nMy in-progress\tjira issue list -a$(jira me) -s\"In Progress\"\nCreate issue\tjira issue create -tType -s\"Summary\" -b\"Description\"\nMove/transition\tjira issue move ISSUE-KEY \"State\"\nAssign to me\tjira issue assign ISSUE-KEY $(jira me)\nUnassign\tjira issue assign ISSUE-KEY x\nAdd comment\tjira issue comment add ISSUE-KEY -b\"Comment text\"\nOpen in browser\tjira open ISSUE-KEY\nCurrent sprint\tjira sprint list --state active\nWho am I\tjira me\nQuick Reference (MCP)\n\nSkip this section if using CLI backend.\n\nIntent\tMCP Tool\nSearch issues\tmcp__atlassian__searchJiraIssuesUsingJql\nView issue\tmcp__atlassian__getJiraIssue\nCreate issue\tmcp__atlassian__createJiraIssue\nUpdate issue\tmcp__atlassian__editJiraIssue\nGet transitions\tmcp__atlassian__getTransitionsForJiraIssue\nTransition\tmcp__atlassian__transitionJiraIssue\nAdd comment\tmcp__atlassian__addCommentToJiraIssue\nUser lookup\tmcp__atlassian__lookupJiraAccountId\nList projects\tmcp__atlassian__getVisibleJiraProjects\n\nSee references/mcp.md for full MCP patterns.\n\nTriggers\n\"create a jira ticket\"\n\"show me PROJ-123\"\n\"list my tickets\"\n\"move ticket to done\"\n\"what's in the current sprint\"\nIssue Key Detection\n\nIssue keys follow the pattern: [A-Z]+-[0-9]+ (e.g., PROJ-123, ABC-1).\n\nWhen a user mentions an issue key in conversation:\n\nCLI: jira issue view KEY or jira open KEY\nMCP: mcp__atlassian__jira_get_issue with the key\nWorkflow\n\nCreating tickets:\n\nResearch context if user references code/tickets/PRs\nDraft ticket content\nReview with user\nCreate using appropriate backend\n\nUpdating tickets:\n\nFetch issue details first\nCheck status (careful with in-progress tickets)\nShow current vs proposed changes\nGet approval before updating\nAdd comment explaining changes\nBefore Any Operation\n\nAsk yourself:\n\nWhat's the current state? — Always fetch the issue first. Don't assume status, assignee, or fields are what user thinks they are.\n\nWho else is affected? — Check watchers, linked issues, parent epics. A \"simple edit\" might notify 10 people.\n\nIs this reversible? — Transitions may have one-way gates. Some workflows require intermediate states. Description edits have no undo.\n\nDo I have the right identifiers? — Issue keys, transition IDs, account IDs. Display names don't work for assignment (MCP).\n\nNEVER\n\nNEVER transition without fetching current status — Workflows may require intermediate states. \"To Do\" → \"Done\" might fail silently if \"In Progress\" is required first.\n\nNEVER assign using display name (MCP) — Only account IDs work. Always call lookupJiraAccountId first, or assignment silently fails.\n\nNEVER edit description without showing original — Jira has no undo. User must see what they're replacing.\n\nNEVER use --no-input without all required fields (CLI) — Fails silently with cryptic errors. Check project's required fields first.\n\nNEVER assume transition names are universal — \"Done\", \"Closed\", \"Complete\" vary by project. Always get available transitions first.\n\nNEVER bulk-modify without explicit approval — Each ticket change notifies watchers. 10 edits = 10 notification storms.\n\nSafety\nAlways show the command/tool call before running it\nAlways get approval before modifying tickets\nPreserve original information when editing\nVerify updates after applying\nAlways surface authentication issues clearly so the user can resolve them\nNo Backend Available\n\nIf neither CLI nor MCP is available, guide the user:\n\nTo use Jira, you need one of:\n\n1. **jira CLI** (recommended):\n   https://github.com/ankitpokhrel/jira-cli\n\n   Install: brew install ankitpokhrel/jira-cli/jira-cli\n   Setup:   jira init\n\n2. **Atlassian MCP**:\n   Configure in your MCP settings with Atlassian credentials.\n\nDeep Dive\n\nLOAD reference when:\n\nCreating issues with complex fields or multi-line content\nBuilding JQL queries beyond simple filters\nTroubleshooting errors or authentication issues\nWorking with transitions, linking, or sprints\n\nDo NOT load reference for:\n\nSimple view/list operations (Quick Reference above is sufficient)\nBasic status checks (jira issue view KEY)\nOpening issues in browser\nTask\tLoad Reference?\nView single issue\tNo\nList my tickets\tNo\nCreate with description\tYes — CLI needs /tmp pattern\nTransition issue\tYes — need transition ID workflow\nJQL search\tYes — for complex queries\nLink issues\tYes — MCP limitation, need script\n\nReferences:\n\nCLI patterns: references/commands.md\nMCP patterns: references/mcp.md"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/jdrhyne/jira",
    "publisherUrl": "https://clawhub.ai/jdrhyne/jira",
    "owner": "jdrhyne",
    "version": "1.3.3",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "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"
  }
}