generate-status-report_skill

This skill generates and publishes project status reports by querying Jira, analyzing progress, and delivering Confluence updates for executives and teams.
  • Python

239

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill atlassian/atlassian-mcp-server --skill generate-status-report

  • SKILL.md11.0 KB

Overview

This skill generates actionable project status reports by querying Jira, analyzing issues, and producing formatted summaries tailored to the audience. It can produce daily, weekly, sprint-based, or custom-period reports and can publish them to Confluence when requested. The skill is interactive and will always clarify scope and publishing details before performing Confluence actions.

How this skill works

The skill builds JQL queries to fetch relevant Jira issues (completed, in-progress, blocked, high priority) and extracts key fields such as key, summary, status, priority, assignee, and timestamps. It analyzes metrics (counts by status, completion rate, high-priority items, unassigned issues), identifies highlights and blockers, and formats the output using an audience-specific template. Finally, it offers to create or update a Confluence page using Markdown-formatted content and asks for space, parent page, and whether to create or update before publishing.

When to use it

  • Create a weekly or daily status report for stakeholders
  • Summarize project progress or recent accomplishments for executives
  • Generate sprint or custom-period reports from Jira issue activity
  • Identify and escalate critical blockers and at-risk items
  • Publish status updates to Confluence for archive and visibility

Best practices

  • Always confirm project key, time period, audience, and Confluence destination before querying Jira
  • Run focused queries for completed, in-progress, blocked, and high-priority issues rather than one large query
  • Link directly to Jira issues in the report and include specific metrics (counts and trends)
  • Use executive template for decision-makers and detailed template for team-level reports
  • Use consistent titles and parent pages in Confluence to make recurring reports easy to find

Example use cases

  • Generate a weekly executive summary for Project PHX showing top 3 highlights and 3 critical blockers
  • Produce a daily standup brief listing yesterday’s completions, today’s plans, and current blockers
  • Create a sprint-end report with completed issues, unresolved blockers, and next-sprint priorities
  • Identify unassigned high-priority issues and recommend action owners for delivery managers
  • Publish a formatted status page under the project’s Confluence space for team visibility

FAQ

I need the Jira project key (or project name to find the key), the reporting period (daily/weekly/sprint/custom), the target audience (executive/team/daily), and whether to publish to Confluence (space and parent page or update an existing page).

Will you publish to Confluence automatically?

No. I will always ask whether you want the report published and confirm the Confluence space, parent page, and whether to create or update before calling the publish action.

What Jira queries are run?

Typical queries include completed in period, in-progress high-priority, blocked issues, and all open issues; queries are built with JQL and run with paging (maxResults default 100).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational