Token导航 LogoToken导航

Agent Skill · 研究检索

jira-atlassian(Jira atlassian 搜索)

用于处理 Jira 项目、任务、缺陷、Sprint、负责人和状态流转。它适合让 Agent 辅助查询工单、汇总迭代进展、创建任务或整理需求和缺陷信息。使用时要确认项目权限、字段配置和工作流规则,不同团队的 Issue 类型、状态和必填字段可能不同;涉及批量改状态、改负责人或创建工单时,应先预览变更内容再执行。

jira-atlassian 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 31,551。

总安装 2,681周安装 114GitHub Stars 公开资料未说明下载 939核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:jira-atlassian(Jira atlassian 搜索)
来源仓库:https://github.com/jeffersonling1217-png/jira-atlassian
安装命令:
openclaw skills install jira-atlassian
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install jira-atlassian

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

全面对接 Atlassian Jira Cloud REST API v3 进行工单全生命周期管理。支持问题创建、状态流转、Sprint 同步及自定义字段操作。适用于敏捷团队的任务跟踪、缺陷管理与迭代进度汇报场景。必须配置正确的 API Token 并限定最小必要权限范围方可安全使用。

jira-atlassian 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install jira-atlassian;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

jira-atlassian 怎么安装?

在终端执行 openclaw skills install jira-atlassian。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

jira-atlassian 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

jira-atlassian 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

jira-atlassian 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

jira-atlassian 用的人多吗?

公开数据是累计安装 2,681 次,近一周安装 114 次,下载 939 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

jira-atlassian 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
jira-atlassian

Jira atlassian 搜索 · 本页

2,681—接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
jira-atlassian
description
|
metadata
author
jeffersonling1217-png
version
1.0.0
clawdbot
emoji
✅
homepage
https://clawhub.ai/jeffersonling1217-png/jira-atlassian
requires
env

Jira Integration

Interact with Atlassian Jira Cloud via REST API v3.

Authentication

Use Basic Auth with email and API token:

Required Environment Variables:

JIRA_EMAIL=your_email@example.com
JIRA_API_TOKEN=your_api_token
JIRA_DOMAIN=your_domain  # e.g. "yourcompany" for yourcompany.atlassian.net

Credentials:

  • Email: $JIRA_EMAIL
  • API Token: $JIRA_API_TOKEN
  • Domain: https://$JIRA_DOMAIN.atlassian.net

Base URL:

https://$JIRA_DOMAIN.atlassian.net/rest/api/3

Jira Software (Agile) Base URL:

https://$JIRA_DOMAIN.atlassian.net/rest/agile/1.0

Generate API Token:

  1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
  2. Click "Create API token"
  3. Label it (e.g., "nanobot")
  4. Copy the token

Common Headers

Content-Type: application/json
Accept: application/json
Authorization: Basic base64(email:token)

Complete API Reference

Total API Summary

CategoryCount
Total Endpoints122
Total Schemas64
Jira Software (Agile)51 endpoints
Builds API9 endpoints
Deployments API7 endpoints
DevInfo API7 endpoints
DevOps Components7 endpoints
Feature Flags6 endpoints
Operations11 endpoints
Remote Links5 endpoints
Security13 endpoints

Jira Software (Agile) API

Boards

Get All Boards
GET /rest/agile/1.0/board

Returns all boards visible to the user.

Create Board
POST /rest/agile/1.0/board

Body:

{
  "name": "Sprint Board",
  "type": "scrum",
  "filterId": 12345,
  "location": {
    "type": "project",
    "projectKeyOrId": "PROJ"
  }
}
Get Board by ID
GET /rest/agile/1.0/board/{boardId}
Delete Board
DELETE /rest/agile/1.0/board/{boardId}
Get Board Configuration
GET /rest/agile/1.0/board/{boardId}/configuration

Returns board configuration including column config, estimation type, and ranking info.

Get Issues for Board
GET /rest/agile/1.0/board/{boardId}/issue

Query params: startAt, maxResults, jql, validateQuery, fields, expand

Move Issues to Board
POST /rest/agile/1.0/board/{boardId}/issue

Body:

{
  "issues": ["PROJ-1", "PROJ-2"],
  "rankBeforeIssue": "PROJ-3",
  "rankAfterIssue": "PROJ-4",
  "rankCustomFieldId": 10001
}
Get Backlog Issues
GET /rest/agile/1.0/board/{boardId}/backlog
Move Issues to Backlog
POST /rest/agile/1.0/backlog/{boardId}/issue

Body:

{
  "issues": ["PROJ-1", "PROJ-2"]
}

Sprints

Get All Sprints
GET /rest/agile/1.0/board/{boardId}/sprint
Create Sprint
POST /rest/agile/1.0/sprint

Body:

{
  "name": "Sprint 1",
  "originBoardId": 1,
  "startDate": "2024-01-15T00:00:00.000Z",
  "endDate": "2024-01-29T00:00:00.000Z",
  "goal": "Sprint 1 goal"
}
Get Sprint
GET /rest/agile/1.0/sprint/{sprintId}
Update Sprint (Full)
PUT /rest/agile/1.0/sprint/{sprintId}

Body:

{
  "name": "Updated Sprint Name",
  "startDate": "2024-01-15T00:00:00.000Z",
  "endDate": "2024-01-29T00:00:00.000Z",
  "goal": "Updated goal",
  "state": "active"
}
Partially Update Sprint
POST /rest/agile/1.0/sprint/{sprintId}

Body:

{
  "name": "Updated Name",
  "goal": "Updated goal",
  "state": "closed"
}
Delete Sprint
DELETE /rest/agile/1.0/sprint/{sprintId}
Get Issues for Sprint
GET /rest/agile/1.0/sprint/{sprintId}/issue
Move Issues to Sprint
POST /rest/agile/1.0/sprint/{sprintId}/issue

Body:

{
  "issues": ["PROJ-1", "PROJ-2"]
}
Swap Sprint
POST /rest/agile/1.0/sprint/{sprintId}/swap

Body:

{
  "sprintToSwapWith": 5
}

Epics

Get Epics for Board
GET /rest/agile/1.0/board/{boardId}/epic
Get Epic
GET /rest/agile/1.0/epic/{epicIdOrKey}
Partially Update Epic
POST /rest/agile/1.0/epic/{epicIdOrKey}

Body:

{
  "name": "Epic Name",
  "summary": "Epic summary",
  "color": "color_1",
  "done": false
}
Get Issues for Epic
GET /rest/agile/1.0/epic/{epicIdOrKey}/issue
Move Issues to Epic
POST /rest/agile/1.0/epic/{epicIdOrKey}/issue

Body:

{
  "issues": ["PROJ-1", "PROJ-2"]
}
Rank Epics
PUT /rest/agile/1.0/epic/{epicIdOrKey}/rank

Body:

{
  "rankBeforeEpic": "EPIC-2",
  "rankAfterEpic": "EPIC-3",
  "rankCustomFieldId": 10001
}
Get Issues Without Epic
GET /rest/agile/1.0/epic/none/issue
Remove Issues from Epic
POST /rest/agile/1.0/epic/none/issue

Body:

{
  "issues": ["PROJ-1", "PROJ-2"]
}

Issue Ranking

Rank Issues
PUT /rest/agile/1.0/issue/rank

Body:

{
  "issues": ["PROJ-1", "PROJ-2"],
  "rankAfterIssue": "PROJ-3",
  "rankBeforeIssue": "PROJ-4",
  "rankCustomFieldId": 10001
}
Get Agile Issue
GET /rest/agile/1.0/issue/{issueIdOrKey}

Returns issue with Agile fields (sprint, closedSprints, flagged, epic).

Get Issue Estimation
GET /rest/agile/1.0/issue/{issueIdOrKey}/estimation?boardId={boardId}
Estimate Issue
PUT /rest/agile/1.0/issue/{issueIdOrKey}/estimation

Body:

{
  "boardId": 1,
  "value": "3h"
}

Accepts formats: "1w", "2d", "3h", "20m" or number (minutes).


Jira Platform API

Issues (CRUD Operations)

Get Issue
GET /rest/api/3/issue/{issueIdOrKey}

Query params: fields, expand, properties, updateHistory Examples:

  • GET /rest/api/3/issue/PROJ-123
  • GET /rest/api/3/issue/PROJ-123?fields=summary,status,assignee
  • GET /rest/api/3/issue/PROJ-123?expand=changelog
Create Issue
POST /rest/api/3/issue

Body:

{
  "fields": {
    "project": { "key": "PROJECT_KEY" },
    "summary": "Issue title",
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        { "type": "paragraph", "content": [{ "type": "text", "text": "Description" }] }
      ]
    },
    "issuetype": { "name": "Task" },
    "priority": { "id": "3" },
    "assignee": { "accountId": "USER_ACCOUNT_ID" }
  }
}
Edit Issue
PUT /rest/api/3/issue/{issueIdOrKey}

Body:

{
  "fields": {
    "summary": "Updated summary",
    "description": { ... }
  },
  "update": {
    "labels": [
      { "add": "bugfix" },
      { "remove": "blocker" }
    ]
  }
}
Delete Issue
DELETE /rest/api/3/issue/{issueIdOrKey}?deleteSubtasks=true
Assign Issue
PUT /rest/api/3/issue/{issueIdOrKey}/assignee

Body:

{
  "accountId": "USER_ACCOUNT_ID"
}

Use "accountId": "-1" for default assignee, null for unassigned.


Search (JQL)

Search Issues
GET /rest/api/3/search?jql={jql}&startAt={offset}&maxResults={limit}&fields={fields}

Query params: jql, startAt, maxResults, fields, expand, properties Examples:

  • GET /rest/api/3/search?jql=project=PMG ORDER BY created DESC
  • GET /rest/api/3/search?jql=assignee=currentUser()&maxResults=50

Issue Operations

Get Transitions
GET /rest/api/3/issue/{issueIdOrKey}/transitions
Transition Issue
POST /rest/api/3/issue/{issueIdOrKey}/transitions

Body:

{
  "transition": { "id": "21" }
}
Add Comment
POST /rest/api/3/issue/{issueIdOrKey}/comment

Body:

{
  "body": {
    "type": "doc",
    "version": 1,
    "content": [
      { "type": "paragraph", "content": [{ "type": "text", "text": "Comment text" }] }
    ]
  }
}
Send Notification
POST /rest/api/3/issue/{issueIdOrKey}/notify

Body:

{
  "subject": "Subject",
  "textBody": "Body text",
  "to": { "reporter": true },
  "restrict": { "group": { "name": "jira-software-users" } }
}

Issue Metadata

Get Create Issue Metadata
GET /rest/api/3/issue/createmeta?projectKeys={project}&issuetypeNames={type}
Get Edit Metadata
GET /rest/api/3/issue/{issueIdOrKey}/editmeta
Get Create Metadata for Project
GET /rest/api/3/issue/createmeta/{projectIdOrKey}/issuetypes
Get Create Metadata for Project & Issue Type
GET /rest/api/3/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}

Bulk Operations

Bulk Create Issues (up to 50)
POST /rest/api/3/issue/bulk

Body:

{
  "issueUpdates": [
    { "fields": { "project": { "key": "PROJ" }, "summary": "...", "issuetype": { "name": "Task" } } },
    { "fields": { "project": { "key": "PROJ" }, "summary": "...", "issuetype": { "name": "Bug" } } }
  ]
}
Bulk Fetch Issues (up to 100)
POST /rest/api/3/issue/bulkfetch

Body:

{
  "issueIdsOrKeys": ["PROJ-1", "PROJ-2", "10005"],
  "fields": ["summary", "project", "status", "assignee"],
  "properties": []
}
Bulk Fetch Changelogs
POST /rest/api/3/changelog/bulkfetch

Body:

{
  "issueIdsOrKeys": ["PROJ-1", "PROJ-2"],
  "fieldIds": ["status", "assignee"],
  "maxResults": 100
}
Get Changelogs
GET /rest/api/3/issue/{issueIdOrKey}/changelog?startAt=0&maxResults=50
Get Changelogs by IDs
POST /rest/api/3/issue/{issueIdOrKey}/changelog/list

Body:

{
  "changelogIds": [10001, 10002]
}

Projects

Get Projects
GET /rest/api/3/project
Get Project
GET /rest/api/3/project/{projectIdOrKey}

Users

Get User
GET /rest/api/3/user?accountId={accountId}
Get Current User (Myself)
GET /rest/api/3/myself
Search Users
GET /rest/api/3/user/search?query={query}&maxResults={limit}

Issue Events

Get Events (Admin)
GET /rest/api/3/events

DevOps Integration APIs

Build Information API

Submit Build Data
POST /rest/builds/0.1/bulk

Note: Requires Connect JWT token or OAuth token for on-premise integration.

Get Build by Key
GET /rest/builds/0.1/pipelines/{pipelineId}/builds/{buildNumber}

Error Handling

StatusMeaning
400Bad request or malformed data
401Invalid credentials or expired token
403Permission denied
404Resource not found
409Conflict
429Rate limited - wait and retry
500Internal server error

Notes

  • JQL (Jira Query Language): Use JQL for powerful issue search and filtering
  • Issue IDs vs Keys: Use PROJ-123 format for keys, numeric ID for direct lookups
  • Transition IDs: Get available transitions first via GET /rest/api/3/issue/{key}/transitions
  • Account IDs: Jira Cloud uses account IDs for users - get them via the users API
  • Bulk Operations: Use bulk endpoints for efficiency when creating/fetching multiple issues
  • Expand: Use ?expand=changelog on issue GET to retrieve full change history

平台分布

OpenClaw

89.4%
按下载量换算839

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills