skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
b-mendoza/agent-skills68 installs

fetching-jira-ticket

Retrieves a Jira ticket into docs/<TICKET_KEY>.md. Use when a Jira URL needs a read-only, validated Markdown snapshot for downstream workflow phases.

How do I install this agent skill?

npx skills add https://github.com/b-mendoza/agent-skills --skill fetching-jira-ticket
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a coordinator for fetching Jira tickets and generating structured Markdown snapshots. It includes specific logic to sanitize external content from Jira by rewriting Markdown headings to prevent data poisoning of the document structure. No security vulnerabilities were detected.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

Fetching Jira Ticket

You are a Jira retrieval coordinator. Keep the coordinator context small: derive the ticket identity, dispatch ticket-retriever, retain only its structured summary, and report the handoff state.

This skill is standalone. Bundled files define the workflow, contracts, and templates. Public URLs in ./references/external-sources.md are optional just-in-time sources for current Jira syntax or progressive-disclosure rationale; normal execution still works from local files when web access is unavailable.

Inputs

InputRequiredExample
JIRA_URLYeshttps://workspace.atlassian.net/browse/PROJ-1234

Derive workspace from the Atlassian subdomain, TICKET_KEY from the final path segment, and project from the key prefix. Pass the full JIRA_URL to the retriever because it carries workspace and ticket identity together.

Subagent Registry

SubagentPathPurpose
ticket-retriever./subagents/ticket-retriever.mdReads Jira data, writes and validates docs/<TICKET_KEY>.md, returns a compact fetch summary

Read the subagent file only when dispatching it.

Progressive Disclosure Map

NeedLoad
Coordinate routing and dispatchThis SKILL.md
Status semantics, exact summary lines, report phrasing./references/fetch-contract.md
Jira retrieval procedure and validation gate./references/retrieval-playbook.md inside ticket-retriever
Markdown snapshot shape./references/ticket-snapshot-template.md only during assembly
Current public docs or source-backed rationale./references/external-sources.md, then fetch only the relevant URL
Retriever behavior./subagents/ticket-retriever.md only when dispatching

The coordinator passes reference paths to the retriever instead of loading detailed playbooks or raw Jira data. Keep only identifiers, the artifact path, structured statuses, counts, warnings, and fatal reasons.

Dispatch Pattern

JIRA_URL: <input URL>
FETCH_CONTRACT_PATH: ./references/fetch-contract.md
RETRIEVAL_PLAYBOOK_PATH: ./references/retrieval-playbook.md
SNAPSHOT_TEMPLATE_PATH: ./references/ticket-snapshot-template.md
EXTERNAL_SOURCES_PATH: ./references/external-sources.md

Branch on the structured summary, not prose:

Summary stateCoordinator action
FETCH: PASS with Validation: PASSReport success and continue
FETCH: PARTIAL with Validation: PASSReport success with visible warnings; continue only if downstream phases tolerate partial context
Validation: FAILStop and report the contract failure
FETCH: FAILStop and report Failure category plus Reason
FETCH: ERRORStop and report the unexpected failure

If a returned status pairing is inconsistent, load ./references/fetch-contract.md and treat the run as an error unless that contract defines a safer action.

Output Contract

The retriever writes at most one local workflow snapshot:

docs/<TICKET_KEY>.md

Leave the snapshot in place and unstaged for workflow resumability. Load ./references/fetch-contract.md only when you need exact summary ordering, count semantics, heading order, or final report phrasing.

Escalation

Stop and surface the retriever's structured failure when the summary reports BAD_INPUT, NOT_FOUND, AUTH, TOOLS_MISSING, RATE_LIMIT, UNEXPECTED, or Validation: FAIL. Ask the user for input only when the failure is actionable by the user, such as a malformed URL or missing authentication.

Examples

<example> Input: `JIRA_URL=https://workspace.atlassian.net/browse/PROJ-1234`

Flow: derive PROJ-1234, dispatch ticket-retriever, receive FETCH: PASS and Validation: PASS, then report docs/PROJ-1234.md, the ticket identity, counts, warnings, and that Jira was not modified. </example>

<example> Input: `JIRA_URL=https://workspace.atlassian.net/browse/PROJ-7001`

Flow: dispatch ticket-retriever, receive FETCH: PARTIAL and Validation: PASS, then report the file path and warning. Continue only with the warning visible to downstream phases. </example>

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/b-mendoza/agent-skills/fetching-jira-ticket">View fetching-jira-ticket on skillZs</a>