uipath-agents
Installation
SKILL.md
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
solutionverb once per session before the first scaffold or deploy. Runuip solution init --help --output json. ResultSuccess→ usesolution initandsolution deploy run --parent-folder-path/--parent-folder-key(post-rename, default).unknown command/ non-zero exit → CLI predates the rename; substituteuip solution new <Name>and--folder-path/--folder-key(same arguments otherwise) wherever this skill calls those. - Greenfield coded agents — scaffold with
uip codedagent new, never hand-author the project. Building a NEW coded agent from scratch: always create it withuip codedagent new <name>, then generate schemas withuip codedagent init— never hand-writepyproject.toml/main.py/langgraph.json/entry-points.jsonyourself, even for a trivial agent. Hand-authoring skips required project structure and produces invalid packages. (Existing or Studio Web local-workspace projects: do NOT runuip codedagent new— follow the project-state gating in coded/quickstart.md.) - 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 instanceassets,queues,processes,buckets,indexes,connections,apps,MCP servers, orInvokeProcess|CreateTask|CreateEscalation(...).
Project Type Detection
Determine the agent mode before proceeding: