什么是 Atlassian CLI (acli)？

Atlassian CLI (acli) 技能在您的终端和 Atlassian 生态系统之间提供了一个强大的桥梁，实现了对 Jira Cloud 和组织级设置的无缝管理。它允许用户执行广泛的操作，包括创建、编辑、搜索和转换工作项，以及管理项目、看板和迭代。通过将此工具集成到 Openclaw Skills 中，开发人员和管理员可以简化工作流程并减少上下文切换。

除了基本任务管理外，此技能还支持高级组织管理，如用户管理和身份验证配置。它旨在与现有的 acli 安装配合使用，为 AI 代理提供一种结构化的方式来安全高效地与 Atlassian 服务进行交互。无论您是在自动化日常更新还是执行复杂的批量操作，此技能都能确保与 Atlassian 云基础设施的高性能交互。

下载入口:https://github.com/openclaw/skills/tree/main/skills/peetzweg/atlassian-cli

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Atlassian CLI (acli) 应用场景

• 在开发生命周期中自动创建和分配 Jira 工作项。
• 使用复杂的 JQL 查询对问题执行批量更新或状态转换。
• 直接从终端管理 Atlassian 组织用户并查看身份验证状态。
• 生成和恢复项目存档或管理自定义字段生命周期。
• 通过 Openclaw Skills 利用 Rovo Dev AI 代理功能增强编码和项目见解。

1. 确保系统中已安装 acli 二进制文件，且可通过命令行访问。
2. 使用个人用途的交互式 OAuth 或用于 Openclaw Skills 内自动化的 API 令牌对会话进行身份验证。
3. 确定目标命令组，例如用于工作项的 jira 或用于组织管理的 admin。
4. 使用特定标志执行命令，以便进行过滤（例如 --jql）、格式化（例如 --json）或批量处理。
5. 以首选格式检查命令输出，以确认执行成功或将数据传导至其他工作流。

Atlassian CLI (acli) 配置指南

在使用此技能之前，必须安装 acli 二进制文件。通过运行以下命令验证其可用性：

acli --help

要进行交互式身份验证，请使用基于 Web 的登录：

acli jira auth login --web

对于 Openclaw Skills 中的非交互式环境或 CI/CD 流水线，请使用 API 令牌进行身份验证：

echo "$API_TOKEN" | acli jira auth login --site "your-site.atlassian.net" --email "user@example.com" --token

Atlassian CLI (acli) 数据架构与分类体系

该技能处理并返回由 Atlassian 实体模型结构化的数据。大多数命令支持多种输出格式，以便于解析。

用户可以使用 --generate-json 标志创建用于复杂对象创建的本地模板，并使用 --from-json 标志上传配置。

name: acli
description: "Reference guide for the Atlassian CLI (acli) - a command-line tool for interacting with Jira Cloud and Atlassian organization administration. Use this skill when the user wants to perform Jira operations (create/edit/search/transition work items, manage projects, boards, sprints, filters, dashboards), administer Atlassian organizations (manage users, authentication), or automate Atlassian workflows from the terminal. Covers all acli commands including: jira workitem (create, edit, search, assign, transition, comment, clone, link, archive), jira project (create, list, update, archive), jira board/sprint, jira filter/dashboard, admin user management, and rovodev (Rovo Dev AI agent). Requires an authenticated acli binary already installed on the system."
required_tools:
  - acli
env_vars:
  - name: API_TOKEN
    description: "Atlassian API token for non-interactive Jira authentication (optional — only needed for CI/automation, not for interactive OAuth login)"
    required: false
  - name: API_KEY
    description: "Atlassian Admin API key for organization administration commands (optional — only needed for admin commands)"
    required: false

Atlassian CLI (acli) Reference

Prerequisites

This skill requires acli to be installed and authenticated. The binary is NOT bundled with this skill.

If acli is not installed, guide the user to: https://developer.atlassian.com/cloud/acli/guides/install-acli/

Verify availability:

acli --help

Authentication

Check auth status before running commands:

acli jira auth status
acli admin auth status

If not authenticated, there are three methods:

OAuth (interactive, recommended for users):

acli jira auth login --web

API Token (non-interactive, recommended for CI/automation):

echo "$API_TOKEN" | acli jira auth login --site "mysite.atlassian.net" --email "user@atlassian.com" --token

Admin API Key (for admin commands only):

echo "$API_KEY" | acli admin auth login --email "admin@atlassian.com" --token

Switch between accounts:

acli jira auth switch --site mysite.atlassian.net --email user@atlassian.com
acli admin auth switch --org myorgname

Security

Secret Handling

• Never hardcode tokens or API keys in commands. Always use environment variables ($API_TOKEN, $API_KEY) or file-based input (< token.txt).
• Never log, echo, or display tokens in output. Avoid piping secrets through intermediate files that persist on disk.
• Prefer OAuth (--web) for interactive use. Only use token-based auth for CI/automation where OAuth is not feasible.
• Do not store tokens in shell history. If using echo "$API_TOKEN" | acli ..., ensure the variable is set in the environment rather than inlined as a literal value.

Destructive Operations

The following commands are destructive or irreversible — always confirm with the user before executing:

• acli jira workitem delete — permanently deletes work items
• acli jira project delete — permanently deletes a project and all its work items
• acli admin user delete — deletes managed user accounts
• acli admin user deactivate — deactivates user accounts
• acli jira field delete — moves custom fields to trash

These commands are impactful but reversible:

• acli jira workitem archive / unarchive
• acli jira project archive / restore
• acli admin user cancel-delete — cancels pending deletion
• acli jira field cancel-delete — restores field from trash

Agent safety rules:

1. Never run destructive commands without explicit user confirmation, even if --yes is available.
2. When bulk-targeting via --jql or --filter, first run a search with the same query to show the user what will be affected.
3. Prefer --json output to verify targets before applying destructive changes.
4. Do not combine --yes with destructive bulk operations unless the user explicitly requests unattended execution.

Command Structure

acli  [ ...] {MANDATORY FLAGS} [OPTIONAL FLAGS]

Four top-level command groups:

• acli jira - Jira Cloud operations (workitems, projects, boards, sprints, filters, dashboards, fields)
• acli admin - Organization administration (user management, auth)
• acli rovodev - Rovo Dev AI coding agent (Beta)
• acli feedback - Submit feedback/bug reports

Common Patterns

Output Formats

Most list/search commands support: --json, --csv, and default table output.

Bulk Operations

Target multiple items via:

• --key "KEY-1,KEY-2,KEY-3" - comma-separated keys
• --jql "project = TEAM AND status = 'To Do'" - JQL query
• --filter 10001 - saved filter ID
• --from-file "items.txt" - file with keys/IDs (comma/whitespace/newline separated)

Use --ignore-errors to continue past failures in bulk operations. Use --yes / -y to skip confirmation prompts (useful for automation).

Pagination

• --limit N - max items to return (defaults vary: 30-50)
• --paginate - fetch all pages automatically (overrides --limit)

JSON Templates

Many create/edit commands support --generate-json to produce a template, and --from-json to consume it:

acli jira workitem create --generate-json > template.json
# edit template.json
acli jira workitem create --from-json template.json

Quick Reference: Most Common Operations

Work Items

# Create
acli jira workitem create --summary "Fix login bug" --project "TEAM" --type "Bug"
acli jira workitem create --summary "New feature" --project "TEAM" --type "Story" --assignee "@me" --label "frontend,p1"

# Search
acli jira workitem search --jql "project = TEAM AND assignee = currentUser()" --json
acli jira workitem search --jql "project = TEAM AND status = 'In Progress'" --fields "key,summary,assignee" --csv

# View
acli jira workitem view KEY-123
acli jira workitem view KEY-123 --json --fields "*all"

# Edit
acli jira workitem edit --key "KEY-123" --summary "Updated title" --assignee "user@atlassian.com"

# Transition
acli jira workitem transition --key "KEY-123" --status "Done"
acli jira workitem transition --jql "project = TEAM AND sprint in openSprints()" --status "In Progress"

# Assign
acli jira workitem assign --key "KEY-123" --assignee "@me"

# Comment
acli jira workitem comment create --key "KEY-123" --body "Work completed"

# Bulk create
acli jira workitem create-bulk --from-csv issues.csv

Projects

acli jira project list --paginate --json
acli jira project view --key "TEAM" --json
acli jira project create --from-project "TEAM" --key "NEW" --name "New Project"

Boards & Sprints

acli jira board search --project "TEAM"
acli jira board list-sprints --id 123 --state active
acli jira sprint list-workitems --sprint 1 --board 6

Detailed Command Reference

For complete flag details, parameters, and examples for every command:

• Jira work item commands (create, edit, search, assign, transition, comment, clone, link, archive, attachment, watcher): See references/jira-workitem-commands.md
• All other commands (jira project/board/sprint/filter/dashboard/field, admin, rovodev, feedback): See references/other-commands.md