CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

uipath-insights

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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

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

An exceptionally actionable, well-sequenced CLI skill: exact commands, flags, exit codes, error-recovery branches, and a clean overview-plus-guides structure with all 11 referenced files real and one level deep. The one drag is conciseness — Critical Rule 1's per-command envelope enumeration and the duplicated routing tables inline material that the per-family guides already own.

Suggestions

Split Critical Rule 1: keep the universal envelope facts (`Result`/`Code`/`Data`, PascalCase keys, failure-envelope shape) inline and move the per-command `Instructions`/`Pagination` enumeration into the guides that own those commands, which already list their own output shapes.

Trim the Scope Boundaries table of rows that duplicate Task Navigation and the description's routing (e.g. dashboard and Looker rows that just re-link the same guides), keeping only the true out-of-skill redirects.

Consider condensing the generic 'Reasoning budget' and 'Working style' sections to the few rules that are specific to this skill's commands, since the rest restate general agent behavior.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is information-dense, but Critical Rule 1 is a single ~250-word sentence exhaustively enumerating which commands add `Instructions` and `Pagination` — detail that belongs in the per-family guides — and the Scope Boundaries table duplicates routing already stated in Task Navigation and the description. This matches anchor 3 ("mostly efficient but includes some... content that could be tightened") better than anchor 4's "minor instances", because the Rule 1 enumeration is a substantial inline block, not a trimmable sentence or two.

3 / 5

Actionability

Guidance is fully executable: exact commands with literal flags (`uip login status --output json`, `--time-range <minutes>` with 60/1440/10080/43200 conversions, `--started-after`/`--started-before` in epoch milliseconds), a table mapping each question to a named playbook with its flags and defaults, and exit codes plus envelope keys for every failure mode. This matches anchor 5 (copy-paste ready commands covering the common cases) with no gaps — flag details beyond the overview are deliberately and correctly delegated to the guides.

5 / 5

Workflow Clarity

The Shared Workflow is a numbered sequence (login check → read the named guide → run the playbook → parse `Data`/`Pagination`) with explicit validation and feedback loops: local ValidationError refusals with exit codes, branching on `Retry` (`RetryWillNotFix` vs `RetryLater`), and Rule 18's read-before-write, `--expected-version`, read-back-after-unknown_error, and mandatory `--backup-file` before any delete. This is anchor 5 — clear sequence, explicit validation, and error-recovery loops — including for the destructive dashboard writes.

5 / 5

Progressive Disclosure

The body is an overview that delegates all command detail to 11 one-level-deep reference guides, each verified to exist in references/ with substantive content, all clearly signaled by name in the Task Navigation table with a stated purpose per guide and explicit read-ordering guidance ("Read only the guides the task needs"), plus rules for when no guide is needed. This matches anchor 5 exactly: clear overview, well-signaled flat references, easy navigation.

5 / 5

Total

18

/

20

Passed

Description

75%Weight 40%Scale 1-5

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

A highly specific, well-bounded description that comprehensively catalogs the tool's read and write surface and explicitly routes adjacent use cases to sibling skills. Its one structural weakness is that all positive trigger phrases live in when_to_use rather than the description field itself, leaving the description with a clear "what" but only negative "when" guidance.

Suggestions

Fold a compact positive trigger clause into the description itself (e.g. 'Use when the user asks about job failures, success rates, queue backlog or SLA risk, machine availability, or Insights dashboards'), drawing the strongest natural phrases from when_to_use.

Add one or two plain-language synonyms users actually say ("job failures", "automation health", "why are queue items failing") to the description so it triggers even when only the description field is consulted.

Keep the existing sibling-skill routing sentence — it is effective — but consider trimming the family-by-family enumeration slightly so the added 'Use when' clause does not push the field past its current length.

DimensionReasoningScore

Specificity

The description enumerates many concrete capability areas — "job metrics, failure analysis, and process performance; queue totals, SLA risk, timelines, and failure drill-down; machine availability, fault ranking, and runtime minutes" plus alert/RBAC reads, "Maestro process dashboard reads and writes", "export destination checks", and "Looker dashboard lists and embed URLs" — comprehensive coverage of the tool's surface with no vague filler. Anchor 5 fits; it is not score 4 because the action list covers every command family rather than leaving minor gaps.

5 / 5

Completeness

The "what" is clearly and comprehensively answered, but the description field contains no positive "Use when..." clause — its only trigger guidance is negative routing ("For live Orchestrator records or job start/stop/logs→uipath-platform..."), and the judging guidelines cap completeness at 3 when the description lacks a 'Use when...' clause or equivalent explicit trigger guidance. It is not 2 because the "what" is thorough and negative boundary guidance is present; it is not 4 because positive 'when' triggers are absent from the field rather than merely under-specified.

3 / 5

Trigger Term Quality

Good natural-term coverage in the field itself ("job metrics", "failure analysis", "SLA risk", "machine availability", "embed URL"), but the phrases a user would most naturally say ("job failures", "why are queue items failing", "how many jobs ran") sit in the separate when_to_use frontmatter field rather than the description. It exceeds anchor 3 (keywords present with variations) but falls short of anchor 5's comprehensive synonym coverage within the evaluated text.

4 / 5

Distinctiveness Conflict Risk

A clear niche ("UiPath Insights historical monitoring via `uip insights`") with explicit disambiguation redirects to sibling skills ("→uipath-platform", "→uipath-troubleshoot", "→uipath-rpa", "→uipath-admin") keeps conflict risk minimal. This matches anchor 5 exactly and is more distinct than anchor 4's "minor overlap risk with closely related skills".

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

UiPath/skills

Path

skills/uipath-insights/SKILL.md

Reviewed

Table of Contents

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.