Atlassian Rovo MCP Server is a cloud-hosted bridge that lets compatible AI tools access Atlassian Cloud data and actions through the Model Context Protocol. Developers and project teams use it with Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom, and other Atlassian services, authenticated through OAuth 2.1 or API tokens. The catalogue entries provide skills, MCP connections, and a plugin for using the server.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add atlassian/atlassian-mcp-server --skill generate-status-reportgit clone --depth 1 https://github.com/atlassian/atlassian-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/atlassian/atlassian-mcp-server/generate-status-report)<a href="https://agentmods.dev/skills/atlassian/atlassian-mcp-server/generate-status-report"><img src="https://agentmods.dev/badge/skills/atlassian/atlassian-mcp-server/generate-status-report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/atlassian/atlassian-mcp-server/generate-status-report"><img src="https://agentmods.dev/badge/skills/atlassian/atlassian-mcp-server/generate-status-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 27 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00097 | $0.03867 |
| Opus 5 | $0.00048 | $0.01934 |
| Sonnet 5 | $0.00019 | $0.00773 |
| Haiku 4.5 | $0.00010 | $0.00387 |
Grade A, and why
generate-status-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- generate-status-report — 100% identical, 155 lines differ
- generate-status-report — 97% identical, 184 lines differ
How it starts
The opening of the file, as written. The whole thing — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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:
- Identify scope - Determine project, time period, and target audience
- Query Jira - Fetch relevant issues using JQL queries
- Analyze data - Categorize issues and identify key insights
- Format report - Structure content based on audience and purpose
- 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?"
- If user says yes: Ask for space name or offer to list available spaces
- Determine: New page or update existing page?
- Ask about parent page if creating under a specific section
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago Changed · +107 lines e9fd30be0ae6
- 10d ago First seen · 336 lines · 97 tokens per session scan A d5548b058a84
generate-status-report is a skill published in the GitHub repository atlassian/atlassian-mcp-server (1,026 stars, last pushed today), licensed Apache-2.0. It adds 97 tokens to every session and 3,867 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
kanban-video-orchestrator
Plan and run multi-agent video production pipelines.
sdlc-review
Review Kanban handoffs and route verified outcomes.
teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.