onnokh/atlassian-cli
Overview
This skill helps install, authenticate, run, and troubleshoot the Atlassian Command Line Interface (acli) for Atlassian Cloud products including Jira, Atlassian Admin, and Rovo Dev. It focuses on practical CLI workflows for automation, CI, and interactive use, with guidance on shell completion, secrets handling, and error trace capture. Use it to standardize terminal-based Atlassian operations and scripting patterns.
How this skill works
The skill guides you through OS-specific installation and upgrade paths, then shows authentication options (API tokens, OAuth, or admin API keys) depending on the product you need to access. It emphasizes discovering commands with built-in help, preferring machine-readable output (JSON) for automation, and safe secrets handling by avoiding inline tokens. It also covers enabling shell completion, patterns for bulk operations, and capturing trace IDs for troubleshooting.
When to use it
- Installing or upgrading acli on macOS, Linux, or Windows
- Authenticating for Jira Cloud, Atlassian Admin, or Rovo Dev workflows
- Automating Jira tasks in CI pipelines using --json and jq
- Performing bulk changes where partial failure is acceptable
- Troubleshooting unexpected errors and collecting trace IDs
Best practices
- Prefer package managers (Homebrew, apt, yum) or vetted binaries placed on PATH for installs
- Use API tokens or CI secret storage; avoid passing secrets directly on the command line
- Use --json and jq for reliable parsing in scripts; redirect --csv for tabular exports
- Chain commands with && when later steps depend on prior success; use --ignore-errors for safe bulk runs
- Enable shell completion for your shell to speed discovery and reduce typos
- Capture trace IDs and avoid printing sensitive values in logs or support tickets
Example use cases
- CI job that authenticates with an API token and runs acli jira workitem list --json | jq to validate backlog state
- Org admin automating user provisioning with Atlassian Admin CLI using an admin API key from a secret store
- Developer running acli rovodev run to execute dev tooling workflows against Rovo Dev
- Bulk updating issue fields with --ignore-errors and collecting failures for manual review
- Enabling zsh completion so tab-complete surfaces acli subcommands and flags during interactive sessions
FAQ
Use API tokens stored in your CI secret store and provide them via stdin or environment variables rather than as command-line arguments.
How do I get machine-readable output for scripts?
Add --json to commands and parse output with jq; use --csv for tabular exports redirected to files when needed.
What should I do when acli returns an unexpected error?
Capture the trace ID from the error output and include it in support tickets; retry or use --ignore-errors for bulk operations if appropriate.
