Jira Ops — 技能工具

Name: Jira Ops — 技能工具
Author: Deonte Cooper

Deonte Cooper

🎫 Jira Ops — 技能工具

v1.0.0

Retrieve, analyze, and update Jira tickets directly. Supports MCP-based (recommended) and direct REST API approaches. Trigger phrases: fetch Jira ticket, upd...

0· 59·0 当前·0 累计

by @djc00p (Deonte Cooper)·MIT-0

API工具网络工具开发工具

下载技能包

License

MIT-0

最后更新

2026/4/5

安全扫描

VirusTotal

无害

查看报告

OpenClaw

安全

high confidence

The skill's requirements and instructions line up with its stated purpose (Jira ticket read/update) and it only asks for standard Jira credentials; nothing looks deliberately deceptive or unrelated.

评估建议

This skill appears to do what it says: read and update Jira issues. Before installing or enabling it, verify the following: 1) Only provide a Jira API token scoped with the minimum permissions needed (prefer read or limited write scopes), store it in a secrets manager or env var, and rotate it if exposed. 2) If you plan to use the MCP path, confirm you trust the 'uvx' tool and the 'mcp-atlassian' package source before installing—the SKILL.md recommends installation but the registry metadata does...

详细分析 ▾

ℹ 用途与能力

Name/description match the requested environment variables (JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN) and the described capabilities (search, fetch, update, transition). Minor inconsistency: SKILL.md recommends installing an MCP client via the 'uvx' tool, but the skill metadata does not declare 'uvx' as a required binary or provide an install spec.

✓ 指令范围

SKILL.md only instructs the agent to interact with Jira (via MCP tooling or direct REST API) and to use the declared environment variables. It does not ask the agent to read unrelated files, exfiltrate data to third parties, or access system paths outside the Jira integration context.

ℹ 安装机制

This is an instruction-only skill with no install spec or shipped code (lowest disk risk). It suggests using 'uvx' to install 'mcp-atlassian==0.21.0' but does not provide an install specification or provenance for that package; if you choose MCP, verify the uvx tool and package source before installing.

✓ 凭证需求

The three required environment variables (JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN) are appropriate and expected for a Jira integration. They are sensitive credentials, so least-privilege token scopes and secret storage are advised (the SKILL.md already recommends not hardcoding tokens).

✓ 持久化与权限

The skill does not request persistent system presence (always: false), does not modify other skills' configurations, and has no config-path requirements. It is user-invocable and may be called autonomously by the agent (platform default) but that is not unusual for skills.

安全有层次，运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发，无需署名。

查看条款 ↗

运行时依赖

🖥️ OSLinux · macOS · Windows

版本

latestv1.0.02026/4/5

Initial release. Jira ticket retrieval, analysis, and updates via MCP or REST API. Adapted from everything-claude-code by @affaan-m (MIT)

● 无害

安装命令点击复制

官方npx clawhub@latest install jira-ops

镜像加速npx clawhub@latest install jira-ops --registry https://cn.clawhub-mirror.com

技能文档

Retrieve, analyze, and update Jira tickets with MCP or direct REST API.

When to Activate

Fetching ticket requirements and acceptance criteria
Adding progress comments or status updates
Transitioning ticket status (To Do → In Progress → Done)
Searching for issues via JQL queries
Linking PRs or branches to tickets

Setup

Option A: MCP Server (Recommended)

Install mcp-atlassian via uvx:

{
  "jira": {
    "command": "uvx",
    "args": ["mcp-atlassian==0.21.0"],
    "env": {
      "JIRA_URL": "https://YOUR_ORG.atlassian.net",
      "JIRA_EMAIL": "your.email@example.com",
      "JIRA_API_TOKEN": "your-api-token"
    }
  }
}

Get your API token: https://id.atlassian.com/manage-profile/security/api-tokens

Option B: Direct REST API

Set these environment variables:

JIRA_URL — Jira instance URL
JIRA_EMAIL — Your account email
JIRA_API_TOKEN — API token (never hardcode)

MCP Tools

With mcp-atlassian configured:

jira_search — JQL queries
jira_get_issue — Fetch issue details
jira_create_issue — Create new issues
jira_update_issue — Update fields
jira_transition_issue — Change status
jira_add_comment — Add comments
jira_get_transitions — List available transitions

Analyzing Tickets

Extract from tickets:

Functional requirements — What needs to be built
Acceptance criteria — Testable conditions
Test types — Unit, integration, E2E
Edge cases — Error scenarios, boundary conditions
Dependencies — Linked issues, APIs, systems

Updating Tickets

Workflow	Jira Action
Start work	Transition to "In Progress" + comment branch name
Tests done	Comment with test coverage summary
PR created	Comment with link, transition if needed
Merged	Transition to "Done"

Security

Never hardcode API tokens
Use environment variables or secrets manager
Add .env to .gitignore
Rotate tokens if exposed
Use least-privilege scopes

Retrieve, analyze, and update Jira tickets with MCP or direct REST API.

When to Activate

Fetching ticket requirements and acceptance criteria
Adding progress comments or status updates
Transitioning ticket status (To Do → In Progress → Done)
Searching for issues via JQL queries
Linking PRs or branches to tickets

Setup

Option A: MCP Server (Recommended)

Install mcp-atlassian via uvx:

{
  "jira": {
    "command": "uvx",
    "args": ["mcp-atlassian==0.21.0"],
    "env": {
      "JIRA_URL": "https://YOUR_ORG.atlassian.net",
      "JIRA_EMAIL": "your.email@example.com",
      "JIRA_API_TOKEN": "your-api-token"
    }
  }
}

Get your API token: https://id.atlassian.com/manage-profile/security/api-tokens

Option B: Direct REST API

Set these environment variables:

JIRA_URL — Jira instance URL
JIRA_EMAIL — Your account email
JIRA_API_TOKEN — API token (never hardcode)

MCP Tools

With mcp-atlassian configured:

jira_search — JQL queries
jira_get_issue — Fetch issue details
jira_create_issue — Create new issues
jira_update_issue — Update fields
jira_transition_issue — Change status
jira_add_comment — Add comments
jira_get_transitions — List available transitions

Analyzing Tickets

Extract from tickets:

Functional requirements — What needs to be built
Acceptance criteria — Testable conditions
Test types — Unit, integration, E2E
Edge cases — Error scenarios, boundary conditions
Dependencies — Linked issues, APIs, systems

Updating Tickets

Workflow	Jira Action
Start work	Transition to "In Progress" + comment branch name
Tests done	Comment with test coverage summary
PR created	Comment with link, transition if needed
Merged	Transition to "Done"

Security

Never hardcode API tokens
Use environment variables or secrets manager
Add .env to .gitignore
Rotate tokens if exposed
Use least-privilege scopes

数据来源：ClawHub ↗ · 中文优化：龙虾技能库

OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制

了解定制服务

License

运行时依赖

版本

安装命令 点击复制

技能文档

When to Activate

Setup

Option A: MCP Server (Recommended)

Option B: Direct REST API

MCP Tools

Analyzing Tickets

Updating Tickets

Security

When to Activate

Setup

Option A: MCP Server (Recommended)

Option B: Direct REST API

MCP Tools

Analyzing Tickets

Updating Tickets

Security

安装命令点击复制