CtrlK
BlogDocsLog inGet started
Tessl Logo

uipath-platform

UiPath platform ops via the uip CLI — use for ANY task hitting UiPath Cloud / Orchestrator / Studio Web / Integration Service / Data Fabric / LLM Gateway. Load BEFORE writing code that calls a UiPath API. Covers auth, folders, assets, queues, storage buckets, libraries, webhooks, triggers, processes, jobs, machines, users, roles, sessions, calendars, IS connectors/connections/activities, Data Fabric entities/records/files/choice-sets (`uip df`), BYO LLM product configurations, BYO guardrail (BYOG) configurations, context grounding, traces (execution traces and spans + trace feedback / annotation), licensing. For 'why did X fail' / root-cause→uipath-troubleshoot. For org/tenant audit trail / audit logs / login history→uipath-admin. For `uip solution` lifecycle→uipath-solution. For PDD/SDD design→uipath-planner. For workflow code (.xaml/.cs)→uipath-rpa, .flow (incl. Data Fabric connector nodes)→uipath-maestro-flow, .bpmn→uipath-maestro-bpmn, agents (.py/agent.json)→uipath-agents, Test Manager→uipath-test.

73

Quality

93%

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

86%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 well-structured, highly actionable CLI guide with strong progressive disclosure — a navigation table routes every task to a real one-level-deep reference. It loses a point on conciseness (some reference-grade concept tables and login prose could live in bundle files) and a point on workflow clarity (destructive-op validation is delegated to references rather than surfaced inline).

Suggestions

Move the Key Concepts tables (Robot Types, Folder Types, Asset Types) and the platform hierarchy diagram into a reference file, keeping only a one-line pointer in SKILL.md to trim token cost.

Condense the multi-paragraph interactive-login warning into a short rule plus a single example; the core guidance ('ask the user to run ! uip login') can be stated in two sentences.

Surface a one-line destructive-op validation reminder inline (e.g., 'deletes require explicit per-turn approval — see data-fabric.md Critical Rules') so the body's own workflows carry the checkpoint rather than relying wholly on the reference.

DimensionReasoningScore

Conciseness

The body is dense and largely assumes Claude's competence (CLI commands, contracts, error shapes), but the Key Concepts section (platform hierarchy ASCII, Robot/Folder/Asset type tables) and the lengthy interactive-login prose include some explanation that could be trimmed or moved to references.

4 / 5

Actionability

Concrete, copy-paste-ready commands throughout ('uip login status --output json', 'uip or folders list', 'uip df files upload <entity-id> <record-id> <field-name> --file <path>'), with explicit 'NOT' anti-patterns covering the common cases.

5 / 5

Workflow Clarity

The Quick Start is a clear Step 1–4 sequence with an explicit validation checkpoint ('Always check first... if it reports Logged in, skip'), and the diagnostic-intent routing is well-sequenced; destructive-op validation is correctly delegated to data-fabric.md rather than inlined, leaving only minor checkpoint gaps in the body itself.

4 / 5

Progressive Disclosure

A clean overview SKILL.md with a Task Navigation table mapping each need to one-level-deep reference files; all cited paths (uip-commands.md, data-fabric/*.md, guardrails/byo-configurations.md, licensing/*, etc.) resolve to real bundle files, with well-signaled links and content appropriately split.

5 / 5

Total

18

/

20

Passed

Description

100%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 highly specific, trigger-rich, and complete, with explicit what/when coverage and careful sibling routing that reduces conflict risk. Its only weakness is verbosity — it packs near-when_to_use-level routing detail into the description field — but no rubric dimension penalizes density when the content is concrete rather than fluff.

DimensionReasoningScore

Specificity

Enumerates many concrete capabilities — 'auth, folders, assets, queues, storage buckets, libraries, webhooks, triggers, processes, jobs, machines, users, roles, sessions, calendars' plus Data Fabric/LLM Gateway/guardrail surfaces — giving comprehensive, specific coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' ('Covers auth, folders, assets...') and 'when' ('use for ANY task hitting UiPath...') with concrete trigger phrases and explicit routing to siblings, matching the top anchor.

5 / 5

Trigger Term Quality

Covers natural product names users say ('UiPath Cloud / Orchestrator / Studio Web / Integration Service / Data Fabric / LLM Gateway'), capability nouns, and file extensions (.xaml/.cs, .flow, .bpmn, .py/agent.json) including synonyms, matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche (platform ops via the uip CLI) and explicitly routes adjacent intents to siblings (uipath-troubleshoot, uipath-admin, uipath-solution, uipath-planner, uipath-rpa, etc.), minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

relative_links

Relative link issues: 51 deeper-than-1-level, 12 suspicious

Warning

referenced_paths_exist

Referenced path issues: 86 deeper-than-1-level

Warning

Total

13

/

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.