CtrlK
BlogDocsLog inGet started
Tessl Logo

uipath-insights

UiPath Insights job monitoring and read-only alert inspection via `uip insights` — job execution metrics, failure analysis, and process performance; filter discovery of Insights-active folders, processes, queues, and machines; real-time alert definition, history, delivery, and entitlement reads. Alert writes are not covered. For Orchestrator job start/stop/logs→uipath-platform, root-cause analysis of specific errors→uipath-troubleshoot, RPA workflow authoring→uipath-rpa.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/uipath-insights/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is a lean, well-structured overview that delegates depth to four real reference guides via a clear navigation table, with concrete flags, exit codes, and explicit error-recovery branching throughout.

DimensionReasoningScore

Conciseness

Tightly written procedural guidance that assumes Claude's knowledge — no padding about what UiPath/Insights is — but the 14 Critical Rules plus several sections make the body sizeable, so a few constraints could still be consolidated.

4 / 5

Actionability

Gives concrete flags (`--time-range <minutes>`, `--started-after`/`--started-before` in epoch ms, `--since`/`--until` in epoch seconds), exit codes (1, 3), and exact JSON envelope shapes (`{ Result, Code, Data }`, failure envelope fields), though full command syntax is delegated to the reference guides.

4 / 5

Workflow Clarity

The Shared Workflow is a clear 3-step sequence and Critical Rule 8 supplies explicit feedback loops (branch on Retry: RetryWillNotFix vs RetryLater; 401/403/404 handling), but the core numbered workflow stays high-level ('Read the guide', 'Run the subcommand and parse Data') with the detailed checkpoints living in the rules.

4 / 5

Progressive Disclosure

Well-sectioned overview (When to Use, Critical Rules, Shared Workflow, Task Navigation, Scope Boundaries, Anti-patterns, Completion Output) with a Task Navigation table mapping each task to one of four real one-level-deep reference guides, all of which exist in references/.

5 / 5

Total

17

/

20

Passed

Description

67%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.

The description is specific and well-bounded with strong distinctiveness, but it front-loads the 'what' and the negative routing while leaving the positive trigger phrases to the separate when_to_use field, so completeness and trigger-term quality trail.

Suggestions

Fold a short 'Use when the user says "job failures", "automation health", or asks about alert history/delivery' clause into the description itself so the 'when' is explicit rather than implied.

Add a few natural synonyms (e.g. 'job KPIs', 'automation health', 'alerting') into the description body so trigger-term coverage does not depend solely on when_to_use.

Consider stating the positive use case before the routing exclusions so the skill's own purpose leads the description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'job execution metrics, failure analysis, and process performance', 'filter discovery of Insights-active folders, processes, queues, and machines', 'real-time alert definition, history, delivery, and entitlement reads' — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no positive 'Use when...' clause or equivalent explicit trigger guidance in the description itself — the 'when' is only weakly implied by the capability listing, and the routing clauses ('For Orchestrator job start/stop/logs→uipath-platform...') are negative guidance about other skills.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('job monitoring', 'failure analysis', 'process performance', 'alert definition, history, delivery') but the natural conversational phrases users actually say ('job failures', 'automation health', 'job success rate') live in when_to_use rather than description, so common synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche ('UiPath Insights job monitoring and read-only alert inspection via `uip insights`') and explicitly routes overlapping work to named sibling skills (uipath-platform, uipath-troubleshoot, uipath-rpa) while excluding alert writes, minimizing conflict risk.

5 / 5

Total

16

/

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.

Validation15 / 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
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.