generate-status-report

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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with clear confirmation checkpoints and properly signaled, real reference files. Its main weakness is conciseness: a generic tips section and a redundant full example workflow add tokens beyond what Claude needs.

Suggestions

Trim the 'Tips for Quality Reports' section to Jira/Confluence-specific guidance only; drop generic advice like 'Lead with the most important information', 'Celebrate significant wins', and 'Include specific numbers and metrics' that Claude already knows.

Cut or heavily condense the 'Complete Example Workflow' section, which re-demonstrates Steps 1-5 already covered above — a single concrete publish call would carry the same lesson at a fraction of the length.

Move the four inline JQL query blocks and the full Confluence tool-parameter templates into the existing references/jql-patterns.md and references/report-templates.md files, keeping SKILL.md a lean overview that points to them.

Dimension	Reasoning	Score
Conciseness	Most content is efficient procedural knowledge Claude lacks (MCP tool names, JQL, parameters), but the 'Tips for Quality Reports' section is generic writing advice and the 'Complete Example Workflow' largely restates Steps 1-5, so it is mostly efficient with some unnecessary padding rather than fully lean.	2 / 3
Actionability	Provides concrete, executable guidance: named MCP tools with parameter signatures (searchJiraIssuesUsingJql, createConfluencePage, updateConfluencePage), copy-ready JQL blocks, and title-format examples, exceeding the pseudocode/incomplete anchor at 2.	3 / 3
Workflow Clarity	A clearly sequenced five-step workflow with explicit confirmation checkpoints ('ASK before proceeding', 'ALWAYS ASK') and a get-then-update sequence for existing pages, matching the explicit-checkpoint anchor rather than the implicit-checkpoint anchor at 2.	3 / 3
Progressive Disclosure	Points to three real one-level-deep bundle files (scripts/jql_builder.py, references/jql-patterns.md, references/report-templates.md) signaled both inline and in a dedicated Resources section, giving clear navigation rather than the weakly-signaled structure at 2.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, uses natural trigger terms, explicitly covers both what the skill does and when to use it, and occupies a clear niche unlikely to conflict with other skills. It uses the standard third-person imperative voice with no first/second-person language to penalize.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Generate project status reports from Jira issues and publish to Confluence', 'categorizes by status/priority', and 'creates formatted reports', matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both what ('Queries Jira issues, categorizes... creates formatted reports') and when via the 'When an agent needs to: (1)...(5)...' trigger clause, so it is not capped at 2 for a missing trigger clause.	3 / 3
Trigger Term Quality	Includes natural terms users would actually say — 'status report', 'weekly/daily reports', 'blockers', 'publish to Confluence' — giving good coverage rather than the partial keyword set at 2.	3 / 3
Distinctiveness Conflict Risk	The Jira-to-Confluence status-report niche with distinct triggers is clearly distinguishable and unlikely to fire for an unrelated skill, fitting the clear-niche anchor rather than the overlap-prone anchor at 2.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/atlassian-rovo/skills/generate-status-report/SKILL.md
Commit: 11c74d6

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.