Every Rovo tutorial shows you the form. Almost none of them show you a finished agent. Atlassian ships 26 of its own, ready to use, and the Atlassian Community has documented real custom ones teams built on top. This page is the gallery: named, worked examples, grouped so you can find the one closest to what you’re trying to do and go build that — not another abstract “here’s how an agent works” walkthrough.

Atlassian’s own 26, grouped by job

Per Atlassian’s out-of-the-box agents documentation, these ship pre-built — open Rovo Chat and use them, no Studio setup required. Grouped exactly as Atlassian groups them:

Documentation & writing

  • Product Requirements Guide — drafts and evaluates PRDs, using “direct language, empathizes with the customer problem, provides evidence”
  • Release Notes Drafter — summarizes up to 20 Jira work items at once, categorized thematically
  • Brand Voice Crafter — generates content matching your org’s guidelines, for quick comms ideation
  • Social Media Writer — creates or refines posts for engagement
  • Global Translator — converts writing into multiple languages
  • Meeting Insights — reads Loom transcripts stored in Confluence and surfaces decisions, action items, and highlights

Decision making & planning

  • Decision Director — reviews documents against the DACI framework and connects them to relevant org projects
  • OKR Generator — creates, reviews, and searches organizational OKRs
  • Work item Planner — decomposes a project into smaller, actionable tasks
  • Progress Tracker — surfaces real-time project status and priorities

Jira work-item management

  • Jira Coding Agent — generates code from Jira context in a secure cloud sandbox and opens pull requests
  • Jira Triage Agent — reviews incoming work items and recommends next steps, including field updates
  • Work item Organizer — moves items into sprints, assigns them to epics, deletes outdated ones
  • Blocker Checker — automation-triggered; flags blocked work items when a rule fires it
  • Bug Report Assistant — structures bug reports with the diagnostic detail they need
  • Readiness Checker — validates work items against your team’s own readiness criteria

Operations & support

  • Rovo Ops — assists incident management and mitigation guidance
  • Service Request Helper — drafts responses using insights from past requests and suggests an assignee
  • Request Resolver — streamlines JSM workflows
  • Request Router — automation-designed; triages incoming requests inside an automation rule

Insight & analysis

  • Jira Theme Analyzer — finds patterns or drafts epics from a JQL query or a project scan
  • Transcript Insights Reporter — turns meeting transcripts into insights and recommendations
  • Customer Insights — analyzes customer feedback from whatever sources you point it at
  • Jira Delivery Agent — flags delivery risk early and turns work-item activity into status updates

Team building

  • User Manual Writer — helps someone document their own working preferences

Help

  • Rovo Expert — introduces Rovo’s features and how to use them

That’s the pattern-match exercise: if your idea is “summarize a set of tickets,” you’re re-describing Release Notes Drafter or Jira Delivery Agent, not inventing something new — go try the built-in first.

Two real custom builds, from the Atlassian Community

The built-ins cover a lot, but not everything — and Atlassian Community’s write-up on real-life Rovo usage documents two agents teams actually configured themselves, with enough specificity to copy the shape:

Support Tickets Analyst. Scoped to a single Jira project (SUPPORT), with a conversation starter of “What were the main trends in the SUPPORT project last month?” It counts tickets created in a given month, groups them into common themes and request types, flags recurring issues and volume spikes, and reports the result in non-technical language — built for project managers and marketing, not engineers. Nothing here is exotic: it’s a knowledge scope plus a well-written conversation starter, the same two Subagent fields covered in the build walkthrough.

Changes Report Assistant. Answers natural-language queries like “Show me all the changes made to the MARC project last week” and exports the answer as Excel or CSV. The detail worth noticing: it’s powered by a third-party marketplace app, Issue History for Jira by SaaSJet, not a built-in Rovo tool — a reminder that a custom agent’s tool list isn’t limited to Atlassian’s own actions if a connector app already exposes the data you need.

Both examples are Studio-shaped — knowledge source, instructions, a couple of tools — not Forge builds. If your version of either needs a system neither Studio’s built-ins nor a marketplace connector reaches, that’s the Studio-vs-Forge decision, not a bigger Studio form.

The trigger detail worth copying

Two of the 26 built-ins — Blocker Checker and Request Router — don’t wait for someone to open Rovo Chat. Per Atlassian’s automation documentation, both are wired to fire from a Jira or JSM Automation rule’s “Use Rovo agent” action: the rule triggers on an event (a field change, a new request), hands the agent a prompt, and the response lands back in a variable the rest of the rule can act on. If your example agent’s job is “watch for X and act,” that automation-rule trigger — not a chat conversation starter — is the piece to copy, and it’s the exact mechanic the how-to-build page walks through step by step.

How to use this list

Found the shape you want? Three questions left, in order:

  1. Can it be built with Studio’s built-in tools (Jira, Confluence, JSM, Google), or does it need a custom action reaching somewhere else? → Rovo Agent Studio vs Forge
  2. What are the actual clicks?How to build a Rovo agent
  3. Does it hold up at your team’s real call volume? A rollup-style agent like Jira Delivery Agent or Progress Tracker is cheap; a chat-triggered FAQ-style agent gets expensive fast at Rovo’s flat 10-credit-per-run pricing. → Which Rovo agents are worth building and Rovo pricing & credits, explained

Found the example, ready to build it — but not the one who wants to be debugging tool selection and knowledge scope by trial and error? We take Rovo agents from spec to deployed, built-in or custom. Configure what you need and see the price and timeline instantly →