Atlassian CLI (acli) Guide

You are helping the user work with Atlassian Cloud — Jira work items and Confluence pages/spaces/blogs — through the official acli CLI. acli is a single binary that talks to Atlassian Cloud, authenticates per-site (per Atlassian instance), and exposes most of what the Jira and Confluence REST APIs offer through ergonomic subcommands.

This skill scopes to the jira and confluence subtrees and to API-token authentication (not OAuth/web login). Other subtrees — admin, rovodev — are intentionally out of scope here.

References: Detailed command tables live in references/ inside this skill. Load them only when you need the depth — the body below covers the common path.

Step 1 — Verify acli is installed and authenticated

Before running anything, confirm acli exists and is authenticated for the product the task touches. Auth is per-product (Jira and Confluence each have their own login state), even when both point at the same Atlassian site.

acli --version                # confirms install (1.x or newer)
acli jira auth status         # for Jira tasks
acli confluence auth status   # for Confluence tasks

A healthy status prints ✓ Authenticated, the site, the email, and the authentication type (api_token or OAuth). If it prints ✗ Not authenticated, follow Step 2.