jiralisted

Read and mutate Jira (Atlassian Cloud or self-hosted Server / Data Center) via the REST API. Supports JQL search with auto-pagination, fetching issues / projects / users, creating and updating issues, applying workflow transitions, adding comments and attachments, deleting issues, listing projects, looking up users, and an arbitrary raw escape hatch. Streams results as JSON, JSONL, or CSV. Handles Cloud (REST v3, basic auth with email + API token, ADF, nextPageToken) vs Server/DC (REST v2, bearer Personal Access Token, plain text, startAt) differences automatically. Use when the user wants to read, search, export, create, update, or transition Jira data.
eugenelim/agent-ready-repo · ★ 7 · Code & Development · score 81

Install: claude install-skill eugenelim/agent-ready-repo

# Jira Client A thin, uniform interface to the Jira REST API. Works against both Atlassian Cloud (`*.atlassian.net`) and self-hosted Server / Data Center installs. **This is for Jira (the issue tracker), not Jira Align (the portfolio product) — those are separate skills with separate credentials.** ## Instructions You are a Jira query agent. Authentication, pagination, retries, ADF wrapping, 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 The CLI auto-detects Cloud vs Server/DC from the base URL host: - `*.atlassian.net`, `*.jira.com`, `*.jira-dev.com` → Cloud. - Anything else → Server / Data Center. Auth schemes differ: | Flavor | Auth | API prefix | JQL endpoint | Description body | |---|---|---|---|---| | Cloud | Basic `base64(email:api_token)` | `/rest/api/3` | `POST /search/jql` (nextPageToken) | ADF (auto-wrapped) | | Server/DC | `Bearer <PAT>` | `/rest/api/2` | `GET /search` (startAt) | Plain string / wiki markup | The CLI handles both transparently. Plain-string `description` / `environment` fields you pass via `--field` are auto-wrapped to ADF on Cloud. ### Configuration location Credentials are resolved by the build-projected `credentials_shim.load_credentials` through the Tier 1 (env) → Tier 2 (OS keyring) → Tier 3 dotfile ladder. The dotfile lives at `~/.agentbundle/credentials.env` (mode 0600 on POSIX; DACL-restricted on Windows).