Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Atlassian aCLI Reference Skill for Jira and Confluence
Reference guide for the Atlassian CLI (acli) - a command-line tool for interacting with Jira Cloud and Atlassian organization administration. Use this skill...
skill openclawclawhub Free
Reference guide for the Atlassian CLI (acli) - a command-line tool for interacting with Jira Cloud and Atlassian organization administration. Use this skill...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/other-commands.md, references/jira-workitem-commands.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- peetzweg
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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
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 <command> [<subcommand> ...] {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
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
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: Jira work item commands (create, edit, search, assign, transition, comment, clone, link, archive, attachment, watcher): See references/jira-workitem-commands.md All other commands (jira project/board/sprint/filter/dashboard/field, admin, rovodev, feedback): See references/other-commands.md
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs
- SKILL.md
- references/jira-workitem-commands.md
- references/other-commands.md