Jira Assistant

Manage Jira issues via Atlassian MCP — search, create, update, transition status, and handle sprint tasks. Auto-detects workspace configuration. Use when user says "create a Jira ticket", "update my sprint", "check Jira status", "transition this issue", "search Jira", or "move ticket to done". Do NOT use for Confluence pages (use confluence-assistant).

7,177 stars 568 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tech-leads-club/agent-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tech-leads-club/agent-skills --skill jira-assistant
Manual install
git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/packages/skills-catalog/skills/(development)/jira-assistant ~/.claude/skills/jira-assistant

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Jira Assistant

You are an expert in using Atlassian MCP tools to interact with Jira.

## When to Use

Use this skill when the user asks to:

- Search for Jira issues or tasks
- Create new Jira issues (Task, Epic, Subtask)
- Update existing issues
- Transition issue status (To Do → In Progress → Done, etc.)
- Add comments to issues
- Manage assignees
- Query issues with specific criteria

## Configuration

**Project Detection Strategy (Automatic):**

1. **Check workspace rules first**: Look for Jira configuration in `.cursor/rules/jira-config.mdc`
2. **If not found**: Use MCP search tools to discover available projects
3. **If still unclear**: Ask user to specify project key
4. **Use detected values** for all Jira operations in this conversation

### Configuration Detection Workflow

When you activate this skill:

1. Check if workspace has `.cursor/rules/jira-config.mdc` with Jira configuration
2. If found, extract and use: Project Key, Cloud ID, URL, Board URL
3. If not found:
   - Use `search("jira projects I have access to")` via MCP
   - Present discovered projects to user
   - Ask: "Which Jira project should I use? (e.g., KAN, PROJ, DEV)"
4. Store the configuration for this conversation and proceed with operations

**Note for skill users:** To configure this skill for your workspace, create `.cursor/rules/jira-config.mdc` with your project details.

## Workflow

### 1. Finding Issues (Always Start Here)

**Use `search` (Rovo Search) first** for general queries:
Read the full skill on GitHub

Details

Skill name
jira-assistant
Path
packages/skills-catalog/skills/(development)/jira-assistant/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Jira Assistant skill do?

Manage Jira issues via Atlassian MCP — search, create, update, transition status, and handle sprint tasks. Auto-detects workspace configuration. Use when user says "create a Jira ticket", "update my sprint", "check Jira status", "transition this issue", "search Jira", or "move ticket to done". Do NOT use for Confluence pages (use confluence-assistant).

How do I install the Jira Assistant skill?

Claude Code plugin: /plugin marketplace add tech-leads-club/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Jira Assistant popular?

It lives in tech-leads-club/agent-skills, which has 7,177 GitHub stars and 568 forks.

Related skills

Frontend Design

7.2k

tech-leads-club/agent-skills

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. Do NOT use for design review or audit (use web-design-guidelines or web-quality-audit).

Frontend & DesignIn 1 list568

Web Design Guidelines

7.2k

tech-leads-club/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).

Frontend & Design568

AI Cold Outreach

7.2k

tech-leads-club/agent-skills

When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.

AI, LLMs & AgentsIn 1 list568

Legacy Migration Planner

7.2k

tech-leads-club/agent-skills

Use when planning legacy system migrations, codebase modernization, monolith decomposition, microservices consolidation, cross-language rewrites, or framework upgrades. Invoke for strangler fig pattern, incremental migration strategy, or refactoring roadmaps. Do NOT use for domain analysis (use domain-analysis), component sizing (use component-identification-sizing), or step-by-step decomposition plans (use decomposition-planning-roadmap).

Software Development568

Gh Address Comments

7.2k

tech-leads-club/agent-skills

Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging (use gh-fix-ci), or general Git operations.

Software Development568

Modular Design Principles

7.2k

tech-leads-club/agent-skills

Technology-agnostic guidance for modular systems: bounded contexts, clear boundaries, composability, state isolation, explicit contracts, failure containment, scaffolding workflows, split/merge criteria, sub-units inside a context, and compliance review signals. Use when designing or reviewing module structure, service boundaries, package layout, cross-cutting dependencies, "how should we split this?", modularity assessments, coupling between domains, greenfield context design, or architecture discussions without assuming a specific framework, language, or repository layout. Do NOT use for exe

Software Development568

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.