← ClaudeAtlas

jira-alignlisted

Read and mutate Jira Align (Atlassian Cloud or self-hosted/on-prem) via the REST API 2.0. Supports fetching individual records (epics, features, stories, capabilities, themes, portfolios, programs, teams, users, etc.), paginating collections with OData-style $filter / $select / $orderby / expand, streaming results as JSON/JSONL/CSV, creating new records, updating existing ones (PUT or PATCH), deleting records, and arbitrary raw calls. Use when the user wants to read, search, export, create, or update Jira Align data.
eugenelim/agent-ready-repo · ★ 7 · AI & Automation · score 81
Install: claude install-skill eugenelim/agent-ready-repo
# Jira Align Client A thin, uniform interface to Jira Align's REST API 2.0. Works against both Atlassian Cloud (`*.jiraalign.com`) and self-hosted / on-prem installs. ## Instructions You are a Jira Align query agent. Authentication, pagination, retries, and output formatting live in `scripts/`. Do not re-implement any of that logic; invoke the CLI with the right subcommand and relay results to the user. ### Flavor support Cloud and on-prem use the same bearer-token authentication flow (the token is generated on each user's Jira Align **Profile → API Token** page). Flavor is auto-detected from the base URL (`*.jiraalign.com` → cloud, anything else → on-prem) and is informational only — auth headers are identical. ### Configuration location Credentials are resolved by the build-projected `credentials_shim.load_credentials` through Tier 1 (env) → Tier 2 (OS keyring) → Tier 3 dotfile. The dotfile lives at `~/.agentbundle/credentials.env`. The declared schema is in `references/creds-schema.toml`: | Key | Required | Notes | |---|---|---| | `JIRAALIGN_BASE_URL` | yes | Cloud: `https://<site>.jiraalign.com`. On-prem: the customer domain. | | `JIRAALIGN_API_TOKEN` | yes | Personal API Token from Jira Align Profile. | | `JIRAALIGN_FLAVOR` | no | `cloud` or `onprem`. Auto-detected from URL host when unset. | Populate any tier by running `credential-setup` skill. ### Security rules (non-negotiable) - Secrets live only in `~/.agentbundle/credentials.env` (mode 0600 on POSIX;