uipath-agents

name: uipath-agents description: "End-to-end work with UiPath Agents of all types: build, integrate with UiPath Products (e.g., Orchestrator, Flow, Maestro), design with UiPath Tools (e.g., Agent Builder/Studio Web), and deploy. Covers Coded Agents (e.g., LangGraph, LlamaIndex, OpenAI Agents) and Low-Code Agents (agent.json / Agent Builder). Excludes coded functions / Functions SDK (separate skill)." when_to_use: "Must use when user mentions or implies any Agent lifecycle phase - e.g., auth, design, scaffold, Studio Web sync, flow integration, editing, pack/deploy/version bump, eval, debug, tracing, guardrails, memory spaces, bindings, attachments. Example requests: 'create/build a UiPath agent', 'build a low-code / Agent Builder agent', 'add agent memory spaces', 'build a coded / Python agent (LangGraph / LlamaIndex / OpenAI Agents)', 'scaffold an agent project', 'run / debug / evaluate / deploy my agent'." allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, WebFetch user-invocable: true

UiPath Agents

Hard Rules

• Treat "build/create/scaffold/implement a UiPath agent" as the full One-Prompt Flow by default. Do not stop after file creation or local run unless the user explicitly says to stop there.
• A normal completion point is after smoke eval and the mandatory Delivery fork question. A final build summary before that is premature unless run/eval is blocked or the user opted out.
• Probe the solution verb once per session before the first scaffold or deploy. Run uip solution init --help --output json. Result Success → use solution init and solution deploy run --parent-folder-path / --parent-folder-key (post-rename, default). unknown command / non-zero exit → CLI predates the rename; substitute uip solution new <Name> and --folder-path / --folder-key (same arguments otherwise) wherever this skill calls those.
• Coded agents only — bindings are always derived from UiPath Python SDK calls and must never be hand-authored. To derive them, always run the sync workflow in coded/lifecycle/bindings-reference.md — scan code, regenerate bindings.json. Without this, resources cannot be overridden per execution environment and will always default to the hardcoded values in the SDK calls. Derive bindings whenever you add, remove, or modify any UiPath SDK resource call — for instance assets, queues, processes, buckets, indexes, connections, apps, MCP servers, or InvokeProcess|CreateTask|CreateEscalation(...).

Project Type Detection

Determine the agent mode before proceeding:

1. Check for existing project files in the working directory:
   • pyproject.toml with uipath dependency + .py files → Coded
   • agent.json with "type": "lowCode" + project.uiproj, AND no pyproject.toml → Low-code
2. No existing project found → ask the user:

   Should I build this as a low-code agent (no Python — configure through prompts and pre-built UiPath tools) or a coded agent (Python — full programmatic control with LangGraph, LlamaIndex, or OpenAI Agents)?

3. If the user needs help deciding, read references/coded-vs-lowcode-guide.md for a capability comparison.

After detection, read the quickstart for that mode before doing anything else:

• Coded → read references/coded/quickstart.md. Quickstart's first step detects project state (greenfield / existing-coded / local-workspace) and gates each lifecycle step on it. For Studio Web Local Workspace specifics, see references/coded/lifecycle/local-workspace.md.
• Low-code → read references/lowcode/lowcode.md

Task Navigation

Resources

• UiPath Python SDK: https://uipath.github.io/uipath-python/
• UiPath Evaluations: https://uipath.github.io/uipath-python/eval/