{
  "markdown": "# Jira Skill for Claude Code\n\nA Claude Code plugin that provides full Jira integration — fetch tickets, search with JQL, manage issues, and generate team digest reports.\n\n## Features\n\n- **Ticket lookup** — fetch full ticket details including description, comments, and image attachments\n- **JQL search** — search Jira with any JQL query\n- **Create issues** — create new tickets with type, priority, assignee, and fix version\n- **Update issues** — modify summary, description, priority, fix version, assignee\n- **Assign / unassign** — assign or unassign tickets by display name\n- **Change status** — transition tickets through workflow states, list available transitions\n- **Link issues** — create relationships between tickets (blocks, relates to, etc.), list available link types\n- **Add comments** — post comments on tickets\n- **Team digest** — generate period reports with per-developer stats, workload analysis, and categorized summaries\n- **Image support** — downloads and analyzes image attachments, opens in system viewer on request\n- **Custom API calls** — access any Jira REST endpoint via `call_api.py` for advanced use cases\n\n## Installation\n\nIn Claude Code, run:\n\n```\n/plugin marketplace add illarion/claude-jira-skill\n/plugin install claude-jira-skill\n```\n\nSee [INSTALL.md](INSTALL.md) for manual installation options.\n\n## Prerequisites\n\n- Python 3.8+\n- A Jira Cloud or self-hosted Jira instance with API token ([create one here](https://id.atlassian.com/manage-profile/security/api-tokens))\n\n## Setup\n\nYou'll need a Jira API token. Create one at [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens).\n\nThen start a Claude Code session and type `/jira login`. The skill will prompt you for your Jira URL, email, and token. Credentials are stored locally in a `.jiraskillrc` file with restricted permissions.\n\n### Multiple Jira instances\n\nIf you work with different Jira instances, place a separate `.jiraskillrc` (by performing a `/jira login` ) in each directory tree. The skill picks up the nearest one automatically — no manual switching needed.\n\n```\n~/work/\n├── a/               ← .jiraskillrc (a.atlassian.net)\n│   ├── repo-1/\n│   └── repo-2/\n└── b/               ← .jiraskillrc (b.atlassian.net)\n    └── repo-3/\n```\n### Multiple projects\n\nDuring login, you can configure default projects (comma-separated, e.g. `FRONTEND,API,MARKETING`). These are used by the team digest to query across all your projects at once.\n\nYou can work with any project your token has access to — just use the project key in your request (e.g. `/jira search open bugs in API2`).\n\n## Usage\n\n| Action | Example |\n|--------|---------|\n| Fetch a ticket | `/jira show me PROJ-1234` |\n| Search | `/jira find all open bugs assigned to me in PROJ` |\n| | `/jira what's overdue in PROJ?` |\n| | `/jira show unassigned tickets in PROJ` |\n| Create an issue | `/jira create a bug in PROJ: \"Login page crashes on empty password\"` |\n| | `/jira create a high priority task in PROJ: \"Update API docs\", assign to Alice` |\n| Update an issue | `/jira change the priority of PROJ-1234 to High` |\n| | `/jira set fix version of PROJ-1234 to 1.5.0` |\n| Add a comment | `/jira comment on PROJ-1234: \"Fixed in latest commit\"` |\n| Assign / unassign | `/jira assign PROJ-1234 to Alice Smith` |\n| | `/jira unassign PROJ-1234` |\n| Change status | `/jira move PROJ-1234 to In Review` |\n| | `/jira what transitions are available for PROJ-1234?` |\n| Link issues | `/jira PROJ-1 blocks PROJ-2` |\n| | `/jira what link types are available?` |\n| Images | `/jira show me the screenshots from PROJ-1234` |\n| | `/jira open screenshot 2` |\n| Team digest | `/jira give me a team digest for last week` |\n| | `/jira what did the team do this week?` |\n\n## Why this over the official Jira MCP?\n\nThe [Atlassian Rovo MCP server](https://www.atlassian.com/platform/remote-mcp-server) gives you basic Jira CRUD — search, create, update. This skill does that and more:\n\n| | Official MCP | This skill |\n|--|:--:|:--:|\n| Search, create, update issues | Yes | Yes |\n| Transitions, assignments, linking | No | Yes |\n| Team digest reports | No | Yes |\n| Developer attribution from changelog | No | Yes |\n| Image attachment analysis | No | Yes |\n| Self-hosted Jira support | No | Yes |\n| Multi-instance auto-switching | No | Yes |\n| ADF formatting handled for you | No | Yes |\n| Requires admin/OAuth setup | Yes | No |\n| Rate limited by Atlassian plan | Yes | No |\n\nThe official MCP is a cloud proxy that requires Atlassian admin to enable Rovo, OAuth 2.1 configuration, and optionally IP allowlisting. This skill runs locally, needs only a personal API token, and works in seconds.\n\n**When to use the official MCP instead:** if you need Confluence or Compass access (not just Jira), your org requires OAuth/SSO and doesn't allow personal API tokens, or corporate policy mandates all API access through Atlassian's managed infrastructure.\n\n## License\n\n[MIT](LICENSE)\n",
  "bytes": 4965,
  "sha": "f81b0e7761a029cbebd25612b90b21f182cb2df9f87b36e20ceeafeaa481d7ea",
  "repo_slug": "illarion/claude-jira-skill",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_illarion_claude_jira_skill_claude_jira_s_c6a58efe/readme"
}