Automates Jira Cloud, Confluence Cloud, and org admin operations via the Atlassian CLI.
npx skills add https://github.com/ahuaracab/test-genesis --skill acli-ahuaracab
Please help me install this Agent Skill. Skill: acli Source: https://github.com/ahuaracab/test-genesis/tree/main/.agents/skills/acli Command: npx skills add https://github.com/ahuaracab/test-genesis --skill acli-ahuaracab
acli) correctly, avoiding silent pagination truncation, auth-scope confusion, and hard-rejected custom-field edits. ## Core Features & Use Cases - Full Jira CLI coverage: create, view, edit, transition, assign, clone, archive, comment on, link, and bulk-operate on work items, plus manage projects, boards, sprints, filters, and dashboards. - Markdown-to-ADF publishing: a bundled converter script turns Markdown into validated ADF JSON for descriptions, comments, and rich-text custom fields, with a documented REST PUT workaround for editing custom fields on existing items. - Confluence and org admin: manage spaces and blog posts, and activate or deactivate users at the organization level with API-key auth. - Use Case: Bulk-transition every story in a fix version from "Ready For QA" to "Done" in a CI job, using JQL selectors with --paginate, --yes, and --ignore-errors so the batch completes non-interactively. ## Quick Start Ask the agent to transition a specific Jira work item to a new status using acli, for example by saying "use acli to move PROJ-123 to In Review".High-intent search queries and answers about installing and using this skill.
Run `acli jira workitem transition --key PROJ-123 --status "In Progress"` after authenticating with `acli jira auth login`. For bulk transitions, pass a `--jql` selector plus `--yes` and `--ignore-errors` so the batch runs non-interactively.
Use API-token auth: pipe the token via stdin with `echo "$ATLASSIAN_API_TOKEN" | acli jira auth login --site <host> --email <email> --token`. OAuth (`--web`) cannot be automated, and each product (jira, confluence, admin) keeps a separate session.
No. `acli workitem edit` hard-rejects every custom-field payload shape with exit 1. The only working path is a REST PUT to `/rest/api/3/issue/{KEY}` with a `{"fields": {customfield_NNNNN: value}}` body using basic auth.
List and search commands silently truncate at the server default of 30-50 rows with no warning. Always pass `--paginate` in automation, or an explicit `--limit N` when a capped result is intentional.
No, acli stores Markdown literally as plain text. Jira rich text requires ADF JSON, so convert Markdown with the bundled md-to-adf.ts script and pass the result via `--from-json`, `--description-file`, or `comment create -F`.
acli cannot enumerate custom fields, manage workflows, issue types, priorities, versions, or components, add items to sprints, upload attachments, or create Confluence pages. These require direct Jira or Confluence REST API calls.
KarlLiveseyRun Atlassian CLI commands to manage Jira and Confluence Cloud tasks.
Lobbi-DocsAutomate Jira issue, sprint, board, and workflow tracking via API.
jpoutrinAttach files to Jira issues and Confluence pages via the Atlassian REST API.
gtheysAutomates Jira and Atlassian admin tasks via the acli binary command line interface.