Name: uipath
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

uipath

UiPath integration. Manage data, records, and automate workflows. Use when the user wants to interact with UiPath data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/uipath/SKILL.md

Quality

Content

67%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 action-dense with executable Membrane CLI commands, a thorough proxy flags table, and a well-sequenced connection state machine with feedback loops. It loses points to an unnecessary intro paragraph, filler lines, and broken step numbering (a stray "1b" and an unlabeled "Step 2").

Suggestions

Remove the opening "UiPath is a robotic process automation (RPA) platform..." paragraph and the filler line "Use action names and parameters as needed" to improve conciseness.

Fix the workflow numbering: rename "#### 1b" to a proper step and label the referenced "Step 2" (Searching for actions) so the sequence is unambiguous.

Move the proxy request flags table and the clientAction schema details into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows ("UiPath is a robotic process automation (RPA) platform... freeing up employees") and filler like "Use action names and parameters as needed," fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flags table, with only minor gaps from unexpanded placeholders like CONNECTION_ID, landing between the 4 and 5 anchors.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts), but broken numbering (a "1b" with no "1a", a referenced "Step 2" that is never labeled) leaves minor gaps below the 5 anchor.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with no bundle files present, so content is appropriately inline; minor gaps are that the proxy flags table and clientAction schema details could live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

70%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 clearly names the UiPath domain and provides an explicit Use-when trigger, satisfying both what and when. It is held back by somewhat generic action verbs and a narrow trigger clause that lacks synonyms like RPA or Orchestrator.

Suggestions

Replace generic verbs with concrete UiPath actions, e.g. "Manage Orchestrator assets, queues, and jobs; automate workflows."

Broaden the trigger clause to include natural synonyms: "Use when the user wants to interact with UiPath, run RPA workflows, or manage Orchestrator queues and jobs."

Add file-format or entity keywords (queues, queue items, robots, schedules) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the UiPath domain plus a few actions ("Manage data, records, and automate workflows"), but those actions are generic and not comprehensive, fitting the 'names domain and 1-2 concrete actions' anchor rather than the 4 anchor's specific action list.	3 / 5
Completeness	Explicitly provides both a "what" ("Manage data, records, and automate workflows") and a "when" ("Use when the user wants to interact with UiPath data"), but the when clause is narrow and could enumerate more concrete triggers, fitting the 4 rather than the 5 anchor.	4 / 5
Trigger Term Quality	Good keyword coverage with natural terms ("UiPath", "data", "records", "workflows", "automate"), but misses common variations/synonyms like RPA, robots, queues, or Orchestrator, so it sits below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The branded "UiPath integration" framing and UiPath-specific trigger make it mostly distinct with minimal conflict risk, though the generic action verbs leave minor overlap risk versus other data-management skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/uipath/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.