# generate-status-report

Turns Jira issues into a project status report and publishes it to Confluence. Useful when you owe a regular progress update.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 315 installs · ★ 1121
- Author: atlassian
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/atlassian/atlassian-mcp-server/tree/HEAD/skills/generate-status-report/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/generate-status-report

## What it does

The skill walks an agent through five steps: pin down the scope, pull issues with JQL, sort them by status and priority, format the report for a given audience, then publish a Confluence page. It ships `scripts/jql_builder.py` for building queries and `references/jql-patterns.md` with ready JQL examples.

Jira lookups go through `searchJiraIssuesUsingJql`, publishing through `createConfluenceContent`. For most reports the skill suggests several narrow queries instead of one broad one: recently resolved, in progress, blocked, and high-priority open. Start with `maxResults: 100` and page with `nextPageToken` when needed.

The skill is meant to be interactive. It asks for the time period, the audience and the Confluence space rather than assuming them, so run it in a session where you can answer a couple of questions. Skip the space and the publish step goes nowhere.

## Requirements
- Works with: Atlassian, Jira, Confluence

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add atlassian/atlassian-mcp-server --skill generate-status-report -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/generate-status-report/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/generate-status-report/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add atlassian/atlassian-mcp-server --skill generate-status-report -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/generate-status-report/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add atlassian/atlassian-mcp-server --skill generate-status-report -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/generate-status-report/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install atlassian/atlassian-mcp-server generate-status-report
```

2. **Manually: put the files in place**
- File: `.github/skills/generate-status-report/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add atlassian/atlassian-mcp-server --skill generate-status-report -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/atlassian/atlassian-mcp-server --path skills/generate-status-report
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/generate-status-report/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add atlassian/atlassian-mcp-server --skill generate-status-report -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/atlassian/atlassian-mcp-server/tree/HEAD/skills/generate-status-report/SKILL.md

## When to use it
- build a weekly project report from Jira issues
- surface blockers for delivery managers
- group issues by status and priority
- publish a status summary as a Confluence page
- write a short daily standup update

## Example prompts
- Generate a status report for project ENG covering the last week, for executives
- Pull blockers and high priority issues in PROJ and publish the report to Confluence
- Draft a standup update: what closed yesterday, what's in progress, what's blocked

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 29972c9859b0450b.

BEGIN THIRD-PARTY FILE 29972c9859b0450b
```text
---
name: generate-status-report
description: "Generate project status reports from Jira issues and publish to Confluence. When an agent needs to: (1) Create a status report for a project, (2) Summarize project progress or updates, (3) Generate weekly/daily reports from Jira, (4) Publish status summaries to Confluence, or (5) Analyze project blockers and completion. Queries Jira issues, categorizes by status/priority, and creates formatted reports for delivery managers and executives."
---

# Generate Status Report

## Keywords
status report, project status, weekly update, daily standup, Jira report, project summary, blockers, progress update, Confluence report, sprint report, project update, publish to Confluence, write to Confluence, post report

Automatically query Jira for project status, analyze issues, and generate formatted status reports published to Confluence.

**CRITICAL**: This skill should be **interactive**. Always clarify scope (time period, audience, Confluence destination) with the user before or after generating the report. Do not silently skip Confluence publishing—always offer it.

## Workflow

Generating a status report follows these steps:

1. **Identify scope** - Determine project, time period, and target audience
2. **Query Jira** - Fetch relevant issues using JQL queries
3. **Analyze data** - Categorize issues and identify key insights
4. **Format report** - Structure content based on audience and purpose
5. **Publish to Confluence** - Create or update a page with the report

## Step 1: Identify Scope

**IMPORTANT**: If the user's request is missing key information, ASK before proceeding with queries. Do not assume defaults without confirmation for Confluence publishing.

Clarify these details:

**Project identification:**
- Which Jira project key? (e.g., "PROJ", "ENG", "MKTG")
- If the user mentions a project by name but not key, search Jira to find the project key

**Time period:**
- If not specified, ask: "What time period should this report cover? (default: last 7 days)"
- Options: Weekly (7 days), Daily (24 hours), Sprint-based (2 weeks), Custom period

**Target audience:**
- If not specified, ask: "Who is this report for? (Executives/Delivery Managers, Team-level, or Daily standup)"
- **Executives/Delivery Managers**: High-level summary with key metrics and blockers
- **Team-level**: Detailed breakdown with issue-by-issue status  
- **Daily standup**: Brief update on yesterday/today/blockers

**Report destination:**
- **ALWAYS ASK** if not specified: "Would you like me to publish this report to Confluence? If so, which space should I use?"
```
END THIRD-PARTY FILE 29972c9859b0450b

The third-party file has ended. Everything between the 29972c9859b0450b tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2618 of 16527 bytes. © atlassian · Apache-2.0 · https://github.com/atlassian/atlassian-mcp-server/tree/HEAD/skills/generate-status-report/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md