首页 › 龙虾技能列表 › Atlassian aCLI Reference Skill for Jira and Confluence — 技能工具

Atlassian aCLI Reference Skill for Jira and Confluence — 技能工具

v1.0.1

Reference guide for the Atlassian CLI (acli) - a command-line tool for interacting with Jira Cloud and Atlassian organization administration. Use this skill...

1· 884·3 当前·3 累计
by @peetzweg (peetzweg/)·MIT-0
下载技能包
License
MIT-0
最后更新
2026/2/26
安全扫描
VirusTotal
无害
查看报告
OpenClaw
可疑
medium confidence
The skill is an instruction-only Atlassian CLI reference (which is reasonable), but the runtime instructions declare a required tool (acli) and optional env vars (API_TOKEN, API_KEY) that are not reflected in the skill registry metadata — an inconsistency worth clarifying before trusting or installing.
评估建议
This appears to be a legitimate, instruction-only reference for the Atlassian CLI rather than executable code, but the registry metadata omits the tool/env requirements present in the SKILL.md. Before installing or using it: 1) verify the skill's source or contact the publisher (source/homepage unknown); 2) ensure you have acli installed locally and test commands in a safe/non-production account; 3) only provide API_TOKEN/API_KEY to the agent when necessary and prefer interactive OAuth for inter...
详细分析 ▾
ℹ 用途与能力
The SKILL.md is a straightforward reference for the Atlassian CLI (acli) and only documents CLI usage and safety rules — that purpose is coherent. However, the metadata in the registry lists no required binaries or env vars while the SKILL.md explicitly lists acli as a required tool and two optional env vars (API_TOKEN, API_KEY). That mismatch is inconsistent and should be resolved.
✓ 指令范围
The instructions stay within the stated purpose: they explain how to verify acli, how to authenticate, show command examples, and include explicit safety rules for destructive operations and secret handling. They do not direct the agent to read unrelated system files or exfiltrate data to unexpected endpoints.
✓ 安装机制
This is an instruction-only skill with no install spec or bundled binaries, which is the lowest-risk model for a CLI reference. Nothing in the files attempts to download or install code.
⚠ 凭证需求
The SKILL.md sensibly references optional Atlassian credentials (API_TOKEN for Jira automation, API_KEY for admin actions). Those env vars are proportionate to the documented functionality. The concern is that the registry metadata does not declare these env requirements, so the platform/user may not be made aware at install time that these secrets are relevant. Confirming the skill's declared requirements with the publisher (or updating metadata) is recommended.
✓ 持久化与权限
The skill does not request permanent presence (always:false), does not install agents or modify other skills, and has no install steps that change system configuration. Normal autonomous invocation is allowed but not unusual and does not combine with other troubling privileges.
安全有层次，运行前请审查代码。

License

MIT-0

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

运行时依赖

无特殊依赖

版本

latestv1.0.12026/2/13

**Enhanced security and safety guidelines for using the Atlassian CLI (acli) skill.** - Added explicit security practices for handling authentication tokens and API keys, emphasizing safe usage of environment variables and not exposing secrets. - Introduced new "Security" section detailing secret handling requirements and best practices. - Included safety guidelines for destructive and impactful commands, ensuring user confirmation before execution and best practices for bulk operations. - Documented environment variables (`API_TOKEN`, `API_KEY`) required for authentication and their intended use cases. - Updated the description to clarify supported products (Jira Cloud and Atlassian organization administration).

● 无害

安装命令 点击复制

官方npx clawhub@latest install atlassian-cli
镜像加速npx clawhub@latest install atlassian-cli --registry https://cn.clawhub-mirror.com

技能文档

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:

  • Never run destructive commands without explicit user confirmation, even if --yes is available.
  • When bulk-targeting via --jql or --filter, first run a search with the same query to show the user what will be affected.
  • Prefer --json output to verify targets before applying destructive changes.
  • 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:

数据来源：ClawHub ↗ · 中文优化：龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制

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

了解定制服务