engineering / skill

uipath-ai-skills

Skills, JSON specifications, Python generators and lint rules for UiPath Studio projects and XAML workflows.

Repository owner marcelocruzrpa

Not rated yet
0 comments

Like 0 Save

Published 11 Oct 2026Listing updated 12 Oct 2026

At a glance

Purpose: Skills, JSON specifications, Python generators and lint rules for UiPath Studio projects and XAML workflows.
Runs in: Local agent with shell
Operating systems: Any
Needs: Runtime: Python 3.10+; Needs internet: Yes; Needs accounts or API keys beyond your agent: Not stated
Files and data: Reads files: Yes; Writes files: Yes; Sends data to other services: Not stated
Tool type: Skill
Delivery: From GitHub
Version: Latest on the main branch
Access: Code on GitHub
Compatibility: According to the README, you can install it as a Claude Code plugin or copy the skill folders for Codex CLI, and a manual install covers other agents. It says it works with other LLMs such as OpenAI GPT. The README lists UiPath Studio 2024.10 or later on Windows for opening generated projects, and says older versions may work. The README says generating and scaffolding projects is cross-platform on Python 3.10 or later, while desktop selector inspection needs Windows and PowerShell.
External costs: The repository is MIT-licensed and states no pricing. Your coding agent or model provider may charge for usage. The README does not say what UiPath Studio costs.
Permissions: The skills act through your coding agent with the access you give it. The README shows Claude Code plugin installation, project-local skill copies and global copies under ~/.codex/skills. The README says scripts scaffold projects, generate and lint XAML, modify framework files and Config.xlsx, and resolve NuGet versions over outbound HTTPS. The README lists file deletion and KillProcess among the activities supported by generated workflows; running workflows that use these activities can delete files or terminate processes. The README's optional Playwright MCP setup runs through npx and opens target pages; its troubleshooting describes inspecting authenticated pages after the user logs in manually. The README instructs browser inspection to remain read-only without credential entry or form submission. The README describes Windows PowerShell inspection of a desktop application's UIA tree after opening the app or asking permission to open it.
Usage terms: MIT License, as stated in the repository. See its LICENSE file for the exact terms.

Code on GitHub

marcelocruzrpa/uipath-ai-skills

MIT

Python108 stars20 forksLast pushed 17 Jul 2026 UTC

AI skills that turns coding agents into UiPath experts.

Topics: agent-skills ai-skills code-generation rpa uipath uipath-rpa

Public GitHub data fetched 13 Oct 2026 UTC · 0 days old

Skill folders in this repository (2)

Folders that contain a SKILL.md file, from GitHub's file list on 13 Oct 2026 UTC.

View on GitHub ↗

What it does

uipath-ai-skills contains uipath-core and uipath-tasks for coding agents working on UiPath Studio projects. The README says the agent writes JSON specifications and Python generators produce XAML from Studio-exported templates.

The README describes uipath-core as covering XAML generation, REFramework scaffolding, selector generation, lint validation and plugin loading. The README says its scripts scaffold sequence, dispatcher and performer projects. The README describes validate_xaml as a lint step with an auto-fix option and rules aimed at LLM error patterns. The README describes uipath-tasks as a plugin for Form Tasks, External Tasks and Task Management activities in human-in-the-loop, system-in-the-loop and recovery workflows.

The README lists building from a Process Definition Document, updating an existing project and refactoring a legacy project into REFramework as usage modes. The README cautions that refactoring is less battle-tested than the other modes and output quality depends on PDD clarity.

Who it is for

People who build or change UiPath Studio projects and want a coding agent to generate the workflows.

Example tasks

Build a UiPath project from a Process Definition Document.
Scaffold a REFramework dispatcher or performer project.
Update an existing project with a bug fix or a new workflow.
Refactor a legacy flat project into REFramework.
Run the lint step on a project with validate_xaml.

Getting started

For Claude Code, the README runs these slash commands: /plugin marketplace add marcelocruzrpa/uipath-ai-skills, /plugin install uipath-core@uipath-ai-skills and /plugin install uipath-tasks@uipath-ai-skills. For Codex CLI or a manual install, it clones the repository and copies the uipath-core and uipath-tasks folders into a skills folder such as .codex/skills or .claude/skills, keeping them side by side. It lists an optional pip install "openpyxl>=3.1.0" for Config.xlsx. The README has the exact commands.

Limitations

The README says its stated test environment is UiPath Studio 2024.10 or later on Windows with Modern UI Automation activities. The README warns that XAML generated against the wrong Studio version band can produce member errors when opening a project, and describes using --band during scaffolding to target a specific band. The README says core generation needs Python 3.10 or later, Config.xlsx operations need openpyxl, and desktop selector inspection needs Windows and PowerShell. The README lists Node.js 18 or later for the optional Playwright MCP server. The README says live web selectors need Playwright MCP; without inspection setup, selectors require manual completion in Studio. The README describes browser inspection as read-only and unable to perform login, but its troubleshooting tells users to log in manually before inspecting an authenticated page. The README says PDD clarity affects output and conversion can require iteration. The README requires uipath-tasks beside uipath-core, marks SAP and Document Understanding plugins as planned, and describes legacy refactoring as less battle-tested. The README suggests increasing project_doc_max_bytes in ~/.codex/config.toml if Codex truncates the skill. The repository can change at any time; check its README before you install.

Data practices

The README says NuGet version resolution uses outbound HTTPS and falls back to cached versions when blocked. The README describes optional Playwright MCP inspection of target web pages, including authenticated pages after the user logs in manually. The README describes desktop inspection as capturing an application's UIA element tree and generation as writing JSON specifications, XAML and project files. The README does not describe telemetry or provider-side retention. What your coding agent and model provider receive depends on how you use the skills.