← ClaudeAtlas

jiralisted

Create, search, and manage JIRA tickets and fetch/edit Confluence pages via REST API
sgtlaugh/skills · ★ 2 · AI & Automation · score 76
Install: claude install-skill sgtlaugh/skills
# JIRA Ticket Management Create, search, and manage JIRA tickets via REST API. ## Setup Credentials live in a JSON file - `$CLAUDE_SKILLS_CREDENTIALS`, default `~/.config/claude-skills/credentials.json` - with `jiraBaseUrl` (e.g. `https://acme.atlassian.net`), `jiraEmail` and `jiraApiToken` (an Atlassian API token). Shell state does not persist between tool calls. Prepend this to EVERY bash call that hits the API: ```bash C=${CLAUDE_SKILLS_CREDENTIALS:-$HOME/.config/claude-skills/credentials.json} JIRA_URL=$(jq -r '.jiraBaseUrl // error("jiraBaseUrl unset in the credentials file")' "$C") || exit 1 JIRA_B64=$(jq -r 'if .jiraEmail and .jiraApiToken then "\(.jiraEmail):\(.jiraApiToken)" | @base64 else error("jiraEmail/jiraApiToken unset in the credentials file") end' "$C") || exit 1 ``` **Important:** Use inline `-H "Authorization: Basic $JIRA_B64" -H "Content-Type: application/json"` directly in each curl call. Do NOT use bash arrays (`JIRA_AUTH=(...)` / `"${JIRA_AUTH[@]}"`) - zsh breaks array expansion in complex commands. Every call uses `-sS --fail-with-body`: an HTTP error prints `curl: (22)` on stderr and still prints Jira's JSON body. **Any `curl: (N)` line on stderr means that call failed** (22 = HTTP error, 6/7 = host unreachable) - in a pipe the exit code is the last command's, so the stderr line is the signal. Report the `errorMessages`/`errors` from the body; presenting a failed call as created/updated/found/empty is WRONG. ## Usage ``` /jira PROJ-123