Jira Ticket
Look up Jira ticket details including summary, type, and description. Use this to fetch ticket context for branch naming, PR creation, or understanding requirements.
Install
$ agentstack add skill-flurdy-agent-skills-jira-ticket ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-flurdy-agent-skills-jira-ticket) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Jira Ticket Lookup
Fetch details about a Jira ticket.
Requirements
This skill requires the mcp-server-atlassian-jira MCP server configured with the name jira.
Usage
/jira-ticket SP-123Instructions
1. Look Up the Jira Ticket
Use the Jira MCP tools to fetch the ticket details:
mcp__jira__jira_get with:
path: /rest/api/3/issue/{ticketNumber}
jq: "{key: key, summary: fields.summary, type: fields.issuetype.name, description: fields.description}"If mcp__jira__jira_get is not yet loaded (common on the first prompt of a session — MCP tools are deferred until first referenced), don't bail out. Instead:
- Call
ToolSearchwithquery: "select:mcp__jira__jira_get"to load its schema. - Retry the
mcp__jira__jira_getcall. - If
ToolSearchreturns no match — thejiraMCP server is not configured for this project, not just lazy-loaded. Tell the user, and either:
- Ask them to paste the ticket summary/description so you can still infer the branch prefix, or
- Point them at the parent project's
~/.claude.jsonmcpServers.jirablock if they want to copy it across (do not edit~/.claude.jsonwithout explicit consent).
Treat a missing MCP server as "ask the user," not as a hard failure.
2. Determine Branch Prefix
Map the Jira issue type to a conventional commit prefix:
| Issue Type | Branch Prefix | |------------|---------------| | Story | feat | | Task | feat | | Bug | fix | | Spike | chore | | Sub-task | inherit from parent, or feat | | Improvement | feat | | Technical Debt | refactor | | Documentation | docs | | Default | feat |
3. Return Ticket Info
Provide the user with:
- Ticket key (e.g.,
SP-123) - Summary
- Issue type
- Suggested branch prefix based on type
- Description (if available and requested)
Example Output
Ticket: SP-123
Summary: Add user authentication
Type: Story
Suggested prefix: feat
Branch name: feat/SP-123-add-user-authenticationSource & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: flurdy
- Source: flurdy/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.