Skills Guide

Jira Issue Lookup

VerifiedCaution

Looks up a Jira issue by key and displays its summary, status, assignee, priority, and direct link. Helps quickly fetch key details from Jira without leaving the IDE.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#jira#issue-lookup#project-management

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Looks up a Jira issue by its key and displays its details (summary, status, assignee, priority, link).

Strengths

  • Quickly view issue details without leaving the terminal
  • Uses environment variables for secure authentication
  • Retrieves key fields like assignee and priority

Limitations

  • Requires base URL configuration and Jira API tokens
  • Only supports Jira REST API v3
  • No caching or advanced error handling
When to use it

When you need to quickly check the status or details of a Jira issue referenced in a conversation or code.

When not to use it

For complex operations like creating, editing, or advanced searching of Jira issues.

Security analysis

Caution
Quality score85/100

The skill uses bash/curl with environment variables for authentication, performing legitimate Jira API queries. However, the command-line exposure of secrets and dependency on the integrity of the config file introduce moderate risk.

Findings
  • •Credentials passed via command line with curl -u, which may be exposed in process listings or system logs.
  • •Relies on config.yaml for baseUrl; if that config is tampered with, credentials could be sent to an attacker-controlled server.
How this analysis is made

Examples

Look up a bug ticket
Look up Jira issue PROJ-123
Check a feature status
What's the status of PROJ-456?

name: jira-lookup description: Look up a Jira issue by key. Shows summary, status, assignee, priority, and link. user-invocable: true arguments: "<JIRA-KEY> (e.g. PROJ-123)"

Jira Issue Lookup

Look up a Jira issue using the REST API and display its details.

Steps

  1. Read config.yaml to get features.jira.baseUrl. If not set, ask the user.
  2. Use $JIRA_EMAIL and $JIRA_TOKEN environment variables for authentication.
  3. Fetch the issue via: 
    curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
  -H "Accept: application/json" \
  "${BASE_URL}/rest/api/3/issue/${JIRA_KEY}?fields=summary,status,assignee,priority"
  4. Display the results:
    • Key: PROJ-123
    • Summary: Issue title
    • Status: In Progress
    • Assignee: Name (or Unassigned)
    • Priority: Medium
    • Link: https://company.atlassian.net/browse/PROJ-123

Error Handling

  • If the issue is not found (404), report "Issue not found".
  • If authentication fails (401/403), report "Authentication failed — check JIRA_EMAIL and JIRA_TOKEN env vars".
  • If baseUrl is not configured, report "Jira base URL not configured — set features.jira.baseUrl in config.yaml".

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/jira-issue-lookup-mm5t89as/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/jira-issue-lookup-mm5t89as' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/jira-issue-lookup-mm5t89as/download' --output '.skill-downloads/jira-issue-lookup-mm5t89as/SKILL.md.part' && mv '.skill-downloads/jira-issue-lookup-mm5t89as/SKILL.md.part' '.skill-downloads/jira-issue-lookup-mm5t89as/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/jira-issue-lookup-mm5t89as/SKILL.md' && test -s '.skill-downloads/jira-issue-lookup-mm5t89as/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/jira-lookup' && cp -R '.skill-downloads/jira-issue-lookup-mm5t89as' '.claude/skills/jira-lookup'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/jira-issue-lookup-mm5t89as'

openskills read 'jira-issue-lookup-mm5t89as'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/jira-issue-lookup-mm5t89as/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot