/uipath-insights

name: uipath-insights
description: "UiPath Insights historical monitoring via `uip insights`: job metrics, failure analysis, and process performance; queue totals, SLA risk, timelines, and failure drill-down; machine availability, fault ranking, and runtime minutes; filter discovery of scope; alert definition, history, delivery, and entitlement reads; Insights user, role, and group reads; Maestro process dashboard reads and writes; export destination checks; Looker dashboard lists and embed URLs. For live Orchestrator records or job start/stop/logs→uipath-platform, root-cause analysis→uipath-troubleshoot, workflow authoring→uipath-rpa, org identity→uipath-admin."
when_to_use: "User says 'job failures', 'automation health', 'job success rate', 'processing time', 'which processes fail the most', 'failure reasons', 'job trends', 'how many jobs ran', 'job metrics or KPIs', 'job timeline', 'process details', 'discover queues', 'which machines reported', 'queue backlog', 'queue SLA', 'why are queue items failing', 'queue retry success', 'machine utilization, availability, or status', 'process dashboard', 'create, update, delete, or copy a dashboard', 'Insights alert', 'which alerts exist', 'alert history or delivery', 'did an alert fire', 'alerting entitlement', 'who has Insights access', 'Insights roles or groups', 'export destination', 'is our export working', 'which Looker dashboards', or 'embed URL'. NOT for listing live jobs or resource CRUD (uipath-platform), alert, RBAC, or export writes, or debugging one job or item (uipath-troubleshoot). Also 'uip insights', 'insights queues'."
allowed-tools: Bash, Read

Reasoning budget

• Match reasoning to step difficulty and bias toward acting. For a mechanical step, if a command

already does the work, run it and read its output instead of re-deriving it.

• Save deep, extended reasoning for the one judgment no command can make: what the data means for

the user, whether a failure rate matters, and what the evidence does not prove.

• None of this licenses a shorter answer. Finish every step the task asked for; where a budget rule

and completeness conflict, completeness wins. These rules cut rework, not required work.

Working style

• **Understand first, then decide.** Read this SKILL.md and the subcommand table in Shared Workflow

before you act, then plan around what the commands actually do rather than a guess.

• **Plan the whole path up front.** Outline the full sequence before running anything.

Critical Rule 2 forbids chaining `uip insights` subcommands in one shell line, so batch by picking the one command that covers the whole question instead of issuing its parts turn by turn.

• **Inspect an input ONCE.** Read a guide or a response once and work from what you have. Never

re-open a file field by field, and never re-run a command whose output is already in context.

• **Don't repeat work.** Do not rerun a command when its inputs and the relevant state are

unchanged, and do not reread an unchanged guide or SKILL.md already in context.

• **Write code once and reuse.** Do not paste near-duplicate inline `python3 -c` or `jq` to compute

something a subcommand already returns.

• **Keep outputs small.** Prefer a projected result over a raw envelope. When a large read needs the

full body, send it to a file and inspect the file.

• **Don't do anything unnecessary.** Do not call tools, read guides, or pull results into context

unless they are needed right now. This governs what you read, never which commands you run.

UiPath Insights

Use `uip insights` for job, queue, and machine monitoring, monitoring-scope discovery, read-only alert inspection, Insights RBAC reads, and Maestro process dashboard reads, create, update, delete, and copy. Read the guide for the task before running commands.

When to Use This Skill

• Job health, success rate, failure count, or processing time across a tenant, folder, or process
• Job trends over time, or a comparison between two periods
• Which processes fail most, and which failure reasons recur
• Whether jobs are stuck, pending, or still running
• Finding the exact folder key, process name, queue name, or machine name to scope a query by
• Queue item throughput, backlog, SLA risk, failure reasons, or how retried items turned out
• Machine health: runtime split, current status and slots, availability over time, fault ranking, or runtime minutes
• Which alerts exist, how one is configured, whether an alert fired, or how a triggered alert is delivered
• Who has Insights access on a tenant, which roles exist and what they permit, and which groups hold them
• What a Maestro process's Monitoring tab shows: its saved dashboard or the template, the global filters saved on it, or creating, changing, removing, or copying that dashboard
• Whether Insights can still reach the organization's export destinations, and which export configurations exist
• Which Looker-era Insights dashboards exist, an embed URL for one, or why an embedded dashboard fails to load

Critical Rules

1. **Use `--output json`.** `jobs` commands return `{ Result, Code, Data }`. Every `jobs investigate` playbook adds `Instructions`, and so do four of the seven plain `jobs` reads (`top-failures`, `failures-by-reason`, `process-details`, `failure-details`), the `filter-*` commands, the `queues` and `machines` commands, the alert commands, and the dashboard commands, and both `looker-dashboards` commands; `filter-*`, every `queues` command except `summary`, every `machines` command except `runtime-mix`, `alerts list`, `alert-history list`, `dashboard-filters list`, `export-configurations list`, and `looker-dashboards list` also add `Pagination`, while no `dashboards` verb does and neither does `export-configurations verify`; that verb adds `Instructions` alone, because its row set is every configuration the organization owns and cannot page. Quote those `Instructions` in the explanation. A failure envelope carries `Result`, `M