How do I install the Fetch Jira Issue skill?

Run npx skillmds@latest add majiayu000/fetch-jira-issue-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Fetch Jira Issue skill do?

name: fetch-jira-issue It is listed under Integrations & APIs on SkillMD.

Is Fetch Jira Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fetch Jira Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fetch Jira Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fetch Jira Issue?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fetch Jira Issue by majiayu000 — Agent Skill

Name: Fetch Jira Issue
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

--- name: fetch-jira-issue description: Use when user mentions a Jira issue key (e.g., PLAT-123) or needs context from Jira. Retrieves and formats issue details for PRISM agent workflows.

Task: Fetch Jira Issue

Purpose

Retrieve and format Jira issue details (Epic, Story, Bug, Task) to provide context for PRISM agent workflows.

When to Use

User mentions a Jira issue key (e.g., PLAT-123)
Agent needs context for decomposition, validation, or implementation
Explicit *jira {issueKey} command

Prerequisites

Jira integration enabled in core-config.yaml
Valid Jira credentials configured
Issue key provided or detected

Process

Step 1: Detect or Request Issue Key

If issue key mentioned in user message:

Extract issue key using pattern from config (default: [A-Z]+-\d+)
Inform user: "I found reference to {issueKey}. Let me fetch the details..."

If no issue key detected:

Ask user: "Great! Let's take a look at that. Do you have a JIRA ticket number so I can get more context?"
Wait for user response
If provided, proceed with fetch
If not provided or user declines, continue without Jira context

Step 2: Read Jira Configuration

Load config values from ../core-config.yaml:

jira:
  baseUrl: {url}
  email: {email}
  token: {token}
  defaultProject: {project}

Validate configuration:

Ensure jira.enabled is true
Verify all required fields present
If missing, inform user and proceed without Jira context

Step 3: Construct API Request

Build Jira REST API URL:

{baseUrl}/rest/api/3/issue/{issueKey}

Prepare authentication:

Use Basic Auth with email:token
Format: Authorization header with base64(email:token)

For WebFetch, construct authenticated URL:

https://{email}:{token}@{hostname}/rest/api/3/issue/{issueKey}

Step 4: Fetch Issue Details

Use WebFetch tool with extraction prompt:

Extract and format the following information from this Jira issue:

## Issue Identification
- Issue Key and Type (Epic/Story/Bug/Task/etc)
- Status and Priority
- Project and Components

## Content
- Summary (title)
- Description (full text, preserve formatting)
- Acceptance Criteria (if present in description or as custom field)

## People & Dates
- Assignee
- Reporter
- Created and Updated dates
- Due Date (if set)

## Estimation & Progress
- Story Points (if applicable)
- Original Estimate
- Time Spent
- Sprint (if applicable)

## Relationships
- Epic Link (what epic this belongs to)
- Parent Issue (if subtask)
- Child Issues (count and list)
- Linked Issues (Blocks, Blocked by, Relates to, etc.)

## Additional Context
- Labels
- Fix Versions
- Last 3 comments (with author and date)
- Attachments (count and types)

Format as a clear, structured markdown summary optimized for development context.
If any field is missing or empty, note it as "Not specified" rather than omitting.

Step 5: Handle Response

Success (200 OK):

Format and display issue summary to user
Store issue data in conversation context for agent reference
Include clickable link: [{issueKey}]({baseUrl}/browse/{issueKey})
Proceed with agent workflow using fetched context

Issue Not Found (404):

Display: "Could not find Jira issue {issueKey}. Please verify the issue key."
Ask user if they want to:
- Try a different issue key
- Search for issues
- Proceed without Jira context

Permission Denied (403):

Display: "Access denied to {issueKey}. This may require different Jira permissions."
Suggest:
- Verify issue key is correct
- Check Jira permissions for the account
- Contact Jira administrator
Offer to proceed without Jira context

Authentication Failed (401):

Display: "Jira authentication failed. Please check credentials in core-config.yaml."
Do not proceed with Jira operations
Continue agent workflow without Jira context

Network/API Error:

Display: "Unable to connect to Jira at this time. Proceeding without issue context."
Log error details for troubleshooting
Continue agent workflow without Jira context

Step 6: Present Formatted Summary

Display format:

## ðŸ“‹ {IssueKey}: {Summary}

**Type:** {Type} | **Status:** {Status} | **Priority:** {Priority}
**Assignee:** {Assignee} | **Reporter:** {Reporter}

### Description
{Description}

### Acceptance Criteria
{Acceptance Criteria or "Not specified"}

### Epic Context
{Epic Link and summary, if applicable}

### Related Issues
- Blocks: {list}
- Blocked by: {list}
- Relates to: {list}
- Child Issues: {count} issues

### Estimation
- Story Points: {points}
- Time Spent: {time}

### Additional Details
- Labels: {labels}
- Components: {components}
- Last Updated: {date}

[View in Jira]({link})

Step 7: Context Integration

For different issue types:

Epic:

Fetch child issues count
Extract epic goals and scope
Identify existing stories to avoid duplication

Story:

Extract acceptance criteria carefully
Note dependencies and blockers
Check for technical notes in comments

Bug:

Extract reproduction steps from description
Review existing comments for additional context
Note severity and customer impact

Task:

Extract deliverables and requirements
Check for related technical documentation
Note any dependencies

Step 8: Offer Follow-up Actions

Based on issue type and agent, offer:

"Would you like me to fetch the epic details?" (if story has epic link)
"Shall I retrieve all child stories?" (if epic has children)
"Would you like to see the linked issues?" (if has dependencies)
"Ready to proceed with {agent task}?" (to continue workflow)

Error Recovery

Invalid Issue Key Format:

Display: "'{input}' doesn't match Jira issue key format (e.g., PLAT-123)"
Ask for correct issue key or offer to proceed without

Multiple Issue Keys Detected:

List all detected keys
Ask user which one to fetch first
Offer to fetch all

Jira Configuration Missing:

Display: "Jira integration not configured. Proceeding without issue context."
Continue agent workflow
Do not block on missing Jira config

Agent-Specific Integration

Story Master (sm):

When decomposing epic: fetch epic + all existing child stories
When creating story: check for duplicate summaries in epic
When estimating: review similar completed stories (if available)

Product Owner (po):

When validating story: fetch full acceptance criteria
When refining: check for missing fields or incomplete descriptions
When prioritizing: review linked dependencies

Support (support):

When investigating bug: fetch full reproduction steps and comments
When creating tasks: link to original bug report
When escalating: include all bug context

QA (qa):

When creating tests: fetch acceptance criteria and edge cases
When validating: check test requirements from story
When reporting: link test results to original story

Dev (dev):

When implementing: fetch technical notes from comments
When fixing bug: review reproduction steps
When completing: verify acceptance criteria met

Architect (architect):

When reviewing epic: fetch scope and technical requirements
When designing: review architectural decisions in comments
When approving: check component relationships

Peer (peer):

When reviewing: fetch story context and acceptance criteria
When approving: verify implementation matches requirements
When suggesting changes: reference architectural constraints

Best Practices

Always ask first if context is ambiguous
Cache fetched data for the conversation session
Format consistently for readability
Handle errors gracefully - never block workflow on Jira failures
Respect privacy - only fetch explicitly referenced issues
Link issues - always include clickable Jira links
Extract acceptance criteria carefully - critical for implementation
Note blocking issues - important for planning
Preserve formatting - maintain description structure
Offer follow-ups - suggest related fetches when relevant

Output

On Success:

Formatted issue summary displayed to user
Issue context available for agent workflow
Clickable Jira link included
Follow-up actions offered

On Failure:

Clear error message
Recovery options offered
Workflow continues without Jira context
No blocking behavior

Completion Criteria

Issue details retrieved or error handled gracefully
Formatted summary displayed to user (if successful)
Issue context integrated into agent workflow
User can proceed with requested task
No workflow blocking on Jira failures

Fetch Jira Issue

File contents

--- name: fetch-jira-issue description: Use when user mentions a Jira issue key (e.g., PLAT-123) or needs context from Jira. Retrieves and formats issue details for PRISM agent workflows.

Task: Fetch Jira Issue

Purpose

When to Use

Prerequisites

Process

Step 1: Detect or Request Issue Key

Step 2: Read Jira Configuration

Step 3: Construct API Request

Step 4: Fetch Issue Details

Step 5: Handle Response

Step 6: Present Formatted Summary

Step 7: Context Integration

Step 8: Offer Follow-up Actions

Error Recovery

Agent-Specific Integration

Best Practices

Output

Completion Criteria

Frequently asked questions

Fetch Jira Issue

File contents

﻿--- name: fetch-jira-issue description: Use when user mentions a Jira issue key (e.g., PLAT-123) or needs context from Jira. Retrieves and formats issue details for PRISM agent workflows.

Task: Fetch Jira Issue

Purpose

When to Use

Prerequisites

Process

Step 1: Detect or Request Issue Key

Step 2: Read Jira Configuration

Step 3: Construct API Request

Step 4: Fetch Issue Details

Step 5: Handle Response

Step 6: Present Formatted Summary

Step 7: Context Integration

Step 8: Offer Follow-up Actions

Error Recovery

Agent-Specific Integration

Best Practices

Output

Completion Criteria

Related skills

Frequently asked questions

How do I install the Fetch Jira Issue skill?

What does the Fetch Jira Issue skill do?

Is Fetch Jira Issue safe to use?

Which AI agents work with Fetch Jira Issue?

Is Fetch Jira Issue free to use?

Who published Fetch Jira Issue?

--- name: fetch-jira-issue description: Use when user mentions a Jira issue key (e.g., PLAT-123) or needs context from Jira. Retrieves and formats issue details for PRISM agent workflows.