🛠️Rovo skills reference

A Rovo skill is a single calculation Rovo can run against your Jira data. Time in Status adds four of them. You don't run a skill directly — you ask an agent a question, and it reaches for the skill that fits. Any agent can use these skills, including agents your team builds.

Before you begin

Skills at a glance

Get time in status while flagged

How long flagged work items sat in each status while they were flagged. A standard Jira report tells you that a work item was flagged; this skill tells you what the flag cost in time and where in your workflow the delay happened.

Ask something like: "Where did flagged work items get stuck last month?"

What you can mention:

• Which work items to cover — a JQL query, a saved filter by ID, or a filter by name

• A date range, which applies regardless of when a sprint started

• Statuses to count, or statuses to ignore — you can leave out flagged time in To Do or Done, where a flag may not be holding up active work

• A time zone (UTC unless you say otherwise)

• A limit on how many work items to include

What you get back:

• Total time spent flagged, as a readable duration

• That time broken down by status, so you can see how much of it fell in each stage

• How many work items were scanned, and how many workflow stages had flagged time

Get sprint report metrics

How a sprint performed, measured against the sprints before it.

Ask something like: "How did this sprint compare to the last three?"

What you can mention:

• The board and the sprint

• How work is estimated — by work item count, by story points, or by original time estimate. This sets the unit for every value the skill returns.

• How many earlier sprints to compare against — up to seven, or none at all (three unless you say otherwise)

• A time zone

What you get back:

• Completion — how many work items were finished, how many were left open, how many were added after the sprint started, and how many were removed from it

• Estimation values — the commitment recorded the moment the sprint started, plus the value completed, left unfinished, added, and removed

• Velocity — the average completed value across the earlier sprints, and how this sprint compares to it

• Distribution — how many work items sit in each status, and how many of each work type

• Sprint details — the sprint name, whether it is active, closed or upcoming, and its start, end, and completion dates

Get time in status for one work item

How long a single work item spent in each status, rebuilt from its change history.

Ask something like: "How long has ABC-123 been in each status?"

What you can mention:

• The work item, by key or by ID

• Whether to recalculate from the work item's change history rather than use its stored values. Recalculating measures working time against a work schedule and returns the full transition history.

• A work schedule, by ID. A schedule carries its own time zone, so giving one sets the time zone as well.

What you get back:

• Total time from creation to now, or to the point the work item closed

• Time spent in each status, with the share of the work item's life that represents

• Every entry into and exit from a status, so you can see whether it moved back and forth between stages

• The work item's summary, for context

Get time in status for work items

The same status timings as the single work item skill, across a set of work items at once.

Ask something like: "Compare time in status for the bugs in this sprint."

What you can mention:

• The work items — a list of up to 40 keys, with repeats dropped automatically

• Whether to recalculate from history rather than use stored values (recalculates unless you say otherwise)

• How many of the work items to process, from 1 to 40

• A work schedule, by ID. A schedule carries its own time zone, so giving one sets the time zone as well.

What you get back: the same breakdown as the single work item skill, for every work item in the set.

Add these skills to your own agent

When you create a Rovo agent, you choose its skills from the skills list. Time in Status skills appear there alongside skills from every other installed app — the [Time in Status] prefix tells you which skills come from this app, and groups them together in the list.

Give your agent skills that match the questions you expect it to answer. An agent that reports on sprints needs the sprint metrics skill; an agent that chases blocked work needs the flagged time skill and one of the time-in-status skills for follow-up detail.

Agents that use these skills

Time in Status ships two agents built on these skills: FlagFocus, for tracking blocked work, and Sprint report insights for sprint reporting. You can use either without building an agent of your own.

Limitations