jira
Provides a Claude Code “skill” that guides an agent to manage JIRA issues, projects, workflows, and Agile/Scrum operations via the Atlassian MCP server (mcp__atlassian). It includes workflow guidance, JQL construction patterns, custom field discovery approaches, templates, and troubleshooting best practices.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture largely depends on the underlying Atlassian MCP server and Jira. This skill recommends providing a JIRA API token via environment variables in .mcp.json, which is better than hardcoding in code, but it does not describe secret redaction/logging behavior, scope minimization, or TLS requirements. No mention of fine-grained OAuth scopes (token-based access instead) or rate-limit/abuse protections within the skill.
⚡ Reliability
Best When
You are using Claude Code (or another agent compatible with the Agent Skill Standard) and have the Atlassian MCP server configured to connect to your Jira instance(s).
Avoid When
You require a standalone JIRA integration (no agent skill/MCP layer), or you cannot provide Jira credentials/tokens securely for the MCP server.
Use Cases
- • Create and update Jira issues (tasks, bugs, stories, epics, subtasks)
- • Construct and run JQL searches and filter for sprint/epic-related queries
- • Manage workflow transitions (including required fields)
- • Perform Agile operations (boards/sprints, add issues to sprints, link issues to epics)
- • Discover and validate custom fields for project-specific schemas
- • Add comments, attachments, and issue links/remote links
- • Batch create issues and gather changelogs for sets of issues
Not For
- • Teams needing a direct Jira API SDK/REST client without an agent “skill” layer
- • Use cases that require complex custom automation beyond the described workflows without consulting the underlying Atlassian MCP tooling
- • Environments where agents cannot run/host the MCP server process (npx/server execution)
Interface
Authentication
Authentication is delegated to the Atlassian MCP server configuration using env vars such as JIRA_API_TOKEN and JIRA_EMAIL. The skill itself is an instruction set and does not define OAuth flows or scope granularity.
Pricing
No pricing information provided in the README content for this skill. Costs would primarily come from Atlassian/Jira usage and the agent runtime/model, not from this repository.
Agent Metadata
Known Gotchas
- ⚠ Authentication/permissions issues will surface as MCP/Jira errors (skill assumes Jira account can create/search/transition as needed).
- ⚠ Jira custom fields and workflow transition validators are project-specific; mismatched field IDs/types or missing required transition fields may cause failures.
- ⚠ Batch operations may be sensitive to rate limits/large result sets; the skill does not explicitly describe pagination/retry strategies in the provided content.
- ⚠ The skill relies on external Atlassian MCP server tooling (installed via npx/global npm), so environment/runtime problems can affect agent behavior.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for jira.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.