// Verify acli installation and authentication. Checks if acli is installed, authenticated to Jira, and can query projects. Use when troubleshooting acli issues or setting up acli for the first time.
| name | acli-setup-check |
| description | Verify acli installation and authentication. Checks if acli is installed, authenticated to Jira, and can query projects. Use when troubleshooting acli issues or setting up acli for the first time. |
| allowed-tools | Bash |
| user-invocable | true |
Verify that the acli CLI tool is installed, authenticated, and can access Jira.
Run the following command to check if acli is available:
which acli
If the command returns a path (e.g., /usr/local/bin/acli), proceed to Step 2.
If the command returns nothing or "not found":
acli is not installed. Please install it from:
https://developer.atlassian.com/cloud/acli/guides/install-acli/
After installation, run:
acli jira auth
Test if acli is authenticated by checking the authentication status:
acli jira auth status 2>&1
This command checks if acli is authenticated and can reach the Jira server without requiring access to specific projects.
Analyze the output:
acli jira auth
If authentication is successful, report success to the user:
✓ acli is installed and authenticated
✓ Connected to: https://redhat.atlassian.net
You're ready to use acli-based Jira skills!
acli jira auth and stopUser: /acli-setup-check
Assistant:
✓ acli is installed at /usr/local/bin/acli
✓ Connected to: https://redhat.atlassian.net
You're ready to use acli-based Jira skills!
Scan a Python package repository for compiled/binary files using Fromager-style detection and malcontent YARA analysis, then triage findings with deterministic rules and AI reasoning to produce a structured risk report section.
Inspect recent git history of a Python package repository for suspicious commits touching supply-chain-sensitive files, then triage findings with AI reasoning to produce a structured risk report section.
Use this skill to evaluate the security of a Python package repository by orchestrating static analysis, binary scanning, and git history inspection sub-skills in parallel, then combining their results into a unified security report with a risk rating.
Run hexora static analysis on a Python package repository to detect suspicious code patterns, then triage findings with deterministic rules and AI reasoning to produce a structured risk report section.
Use this skill to identify non-Red Hat RPM packages installed in container images or on the local machine. For containers, pulls images across multiple architectures and release tags; for local scans, inspects the host directly. Extracts RPM signing metadata and reports packages not signed with the Red Hat GPG key as CSV output. Use when auditing compliance, checking supply-chain provenance, or scanning for third-party RPMs in RHOAI component images.
Sync code from an upstream GitHub repository into a target fork (e.g., opendatahub-io midstream). Detects remotes from the current repo, or clones fresh if run from outside. Fetches upstream, merges into a sync branch, restores protected files, resolves conflicts, and opens a PR to the target GitHub repo. Use when asked to sync upstream, merge upstream changes, or bring a GitHub fork up to date with its upstream source.