- Get started
- Overview
- Install and set up
- Choosing your agent
- Where to run your coding agent
- Your first build
- Best practices
- Capabilities
- Skills
- CLI
- Examples
- Examples overview
- Recipe: build an agent
- Recipe: automate with RPA
- Recipe: enter data into a web app
- Recipe: extract data from a desktop app
- Recipe: refactor and test a workflow
- Recipe: a queue-based process with REFramework
- Recipe: build a Maestro Flow
- Recipe: coded app and API workflow
- Recipe: verify a release with Test Manager
- Recipe: extract data from documents with IXP
- Advanced
- Help
UiPath skills work across several AI coding agents. The right choice is usually the agent you already use day to day, since the UiPath experience is consistent across all of them.
Supported agents
| Agent | Form factor | Notes |
|---|---|---|
| Claude Code | Terminal and IDE | Anthropic's coding agent, available as a CLI and IDE extensions. |
| Cursor | IDE | AI-native code editor. |
| Codex CLI | Terminal | OpenAI's command-line coding agent. |
| Google Antigravity | Agentic development platform | Google's agent-first development platform. |
How skills install per agent
The installer detects the coding agents present on your machine and adds the UiPath skills to each one. The detection and placement are handled for you during uip skills install.
To target a single agent rather than all detected ones, pass its identifier: uip skills install --agent <name>. Run uip skills install --help to see the exact identifiers supported by your CLI version.
Recommendation
The agent your team already works in is usually the best starting point. The UiPath skills, the uip CLI, and the resulting projects are the same regardless of agent, so there is no UiPath-specific reason to switch tools. If you have no existing preference, any of the four is a sound starting point.