Project management · 6 skills

Jira MCP and Claude skills

Pull sprint progress, blocked and stale issues, and bug trends from Jira with JQL, and post a short status your team actually reads.

Connect Jira to your agent (MCP)

Atlassian Rovo MCP Server, Atlassian's official remote server for Jira and Confluence at https://mcp.atlassian.com/v2/mcp. In Claude, add the Atlassian connector from the directory; in Claude Code, run claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp and authenticate with /mcp. It signs in with OAuth 2.1 or an API token and respects your Jira permissions (getting started).
Atlassian CLI. After acli jira auth login, acli jira workitem search --jql "sprint in openSprints()" --json returns the same issues from a terminal.
REST API with an API token. Create a token at id.atlassian.com under Security > API tokens. The skill reads JIRA_EMAIL, JIRA_API_TOKEN and JIRA_BASE_URL (https://acme.atlassian.net) and uses basic auth. A scoped token limited to read:jira-work and read:jira-user is narrower; scoped tokens call https://api.atlassian.com/ex/jira/{cloudId} instead of your site URL.

A classic token can do anything your account can, so prefer a scoped token with read scopes only, or an account that just has Browse permission on the projects in the report.

6 Jira skills

Jira: my open issues, summarized

Each weekday morning: your unresolved Jira issues grouped by priority, with anything overdue or due this week pulled to the top.

DevelopersWeekdays at 8:30Report card

Jira weekly status report

Every Friday afternoon: what got done, what is in flight, what is blocked and what scope was added, written for people who never open Jira.

Product managersFridays at 15:00Report card

Jira sprint progress

Each weekday morning: the share of committed story points done in the open sprint, the days left, and whether the pace so far gets you to the end.

Product managersWeekdays at 9:00Stat tile

Jira stale issues report

Every Monday: To Do and In Progress issues with no update for 14 days or more, oldest first, with their owners and a suggested next move for each.

Product managersMondays at 10:00Report card

Jira blocked issues alert

Twice a day: every flagged or blocked issue in the active sprint, what it waits on and since when, with an ask about who clears it today.

Product managersWeekdays at 9:00 and 14:00Asks you

Jira bug backlog trend

Every Friday: open bugs right now, bugs created and resolved this week, and the eight-week trend, so a bad week is not mistaken for a bad quarter.

DevelopersFridays at 16:00Stat tile

What agents do with Jira

Agents read Jira Cloud with JQL through GET /rest/api/3/search/jql, plus the Agile API for boards and sprints. JQL does the filtering: project = APP AND sprint in openSprints(), statusCategory != Done, assignee = currentUser(), updated <= -14d, Flagged is not EMPTY, issuetype = Bug AND created >= -7d. The fields that end up in reports are status, statusCategory, assignee, priority, labels, created, resolutiondate, duedate and story points, which sit in a site-specific custom field such as customfield_10016. The search endpoint pages with nextPageToken and returns only the fields you name, and the Agile API (/rest/agile/1.0/board/{boardId}/sprint?state=active) adds sprint dates and goals.

What teams run on a schedule: sprint progress split into done, in progress and not started; blocked or flagged issues; tickets nobody touched in two weeks; bugs opened against bugs fixed this week; and a personal morning list of what is assigned to you.

atlassian.com/software/jira

Teams that use these

Your Jira numbers, on one board with everything else

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Join the open beta Browse all skills

Free during the open beta. No card.