skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
delexw/claude-code-misc55 installs

jira-ticket-viewer

View Jira ticket details using the jira CLI (jira-cli). Use when given a Jira issue key to fetch and display ticket information.

How do I install this agent skill?

npx skills add https://github.com/delexw/claude-code-misc --skill jira-ticket-viewer
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubfail

    The skill accesses sensitive local Jira configuration files and handles a Jira API token. A significant security risk is present where the API token could be exfiltrated to malicious external servers because authentication headers are sent to URLs extracted from Jira tickets without domain validation. Additionally, the skill is susceptible to indirect prompt injection from Jira ticket content.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerfail

    3/6 files flagged

What does this agent skill do?

Jira Ticket Viewer

Fetch and display Jira ticket details using the jira CLI tool.

Inputs

Raw arguments: $ARGUMENTS

Infer from the arguments:

  • TICKET_KEY: the Jira issue key
  • OUT_DIR: output directory, or .implement-assets/jira if not provided

System Requirements

  • jira CLI installed and configured (https://github.com/ankitpokhrel/jira-cli)
  • Environment variable JIRA_API_TOKEN set with a valid Jira API token. Important: When checking this variable, verify at least 2 times before concluding it is not set. Environment variables can appear unset due to shell context differences. Never expose the value — use existence checks only (e.g. test -n "$JIRA_API_TOKEN").
  • Environment variable JIRA_SERVER set to the Jira base URL (e.g. https://yourcompany.atlassian.net).

Execution

  1. Pre-flight check: Run jira me to verify the CLI is installed and authenticated — if it fails, follow error handling in references/rules.md. Do NOT continue until jira me succeeds.
  2. Validate TICKET_KEY against references/rules.md
  3. Fetch raw JSON (single API call): Run mkdir -p OUT_DIR && jira issue view TICKET_KEY --raw > OUT_DIR/raw.json via Bash
  4. Parse ticket: Run node ${CLAUDE_SKILL_DIR}/scripts/parse-ticket.js < OUT_DIR/raw.json > OUT_DIR/dossier.json via Bash to get the parsed JSON output
  5. Fetch pull requests: Run node ${CLAUDE_SKILL_DIR}/scripts/fetch-pull-requests.js < OUT_DIR/raw.json > OUT_DIR/pull-requests.json via Bash. If the output is a non-empty array, read OUT_DIR/dossier.json, add a pullRequests field with the array, and save back using the Write tool. PR fetch failure is non-fatal — warn and continue.
  6. Interpret comments: If the parsed JSON contains a non-empty comments array, analyze them following references/comment-rules.md. Replace the comments array in the JSON with a commentSummary object, then save the updated JSON back to OUT_DIR/dossier.json using the Write tool.
  7. Attachments: If the parsed JSON contains a non-empty attachments array, download them:
    • Run node ${CLAUDE_SKILL_DIR}/scripts/download-attachment.js --out OUT_DIR < OUT_DIR/raw.json via Bash
    • Include downloaded attachment file paths in the output
  8. Return the parsed JSON output (see references/output-format.md for schema reference), including attachment download paths if any

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/delexw/claude-code-misc/jira-ticket-viewer">View jira-ticket-viewer on skillZs</a>