aclilisted

# Atlassian CLI Use `acli` for Jira and Confluence Cloud from the shell. Atlassian publishes no skill for `acli` itself, so this skill owns authentication, bounded reads, and the write boundary. ## Workflow 1. **Resolve the account**: `acli auth status`, then `acli auth login` for OAuth or an API token piped on stdin, never as an argument; `acli auth switch` selects the site when several are configured. ```bash acli jira auth login --site <site>.atlassian.net --email <email> --token < token.txt ``` 1. **Bounded reads**: JQL with a limit and explicit fields, JSON for anything a tool parses. ```bash acli jira workitem search --jql 'project = TEAM AND status != Done' --fields key,summary,status --limit 50 --json acli jira workitem view TEAM-123 --fields summary,status,comment --json acli confluence page view --id <page-id> --body-format storage --json ``` 1. **Write with authority**: reuse existing authority for the requested keys, fields, and effects; ask only when consequential scope is missing. Comments, assignments, and bulk operations must be included in that authority. Prefer `--generate-json` then `--from-json` for reproducible creations. ```bash acli jira workitem create --project TEAM --type Task --summary "<summary>" --json acli jira workitem transition --key TEAM-123 --status "In Progress" acli jira workitem comment create --key TEAM-123 --body "<text>" ``` 1. **Verify by reading back**: `view --json` after every mutatio