Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion skills/uipath-agents/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
- 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.
<!--skill-flavor:solution-verb-probe:start-->
- **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.

Check warning on line 16 in skills/uipath-agents/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-agents

Possibly stale `uip solution new` (valid prefix: `solution`)
<!--skill-flavor:solution-verb-probe:end-->
- **Greenfield coded agents — scaffold with `uip codedagent new`, never hand-author the project.** Building a NEW coded agent from scratch: install the framework package in the active venv first, then always create the project with `uip codedagent new <name>` and generate schemas with `uip codedagent init` — never hand-write `pyproject.toml` / `main.py` / `langgraph.json` / `entry-points.json` yourself, even for a trivial agent. Hand-authoring skips required project structure and produces invalid packages. The installed framework package selects the scaffold; after `new`, confirm `<framework>.json` exists — recovery is in [coded/lifecycle/setup.md](references/coded/lifecycle/setup.md) § Verify the Scaffold. (Existing or Studio Web local-workspace projects: do NOT run `uip codedagent new` — follow the project-state gating in [coded/quickstart.md](references/coded/quickstart.md).)
- **Confirm before deleting or uninstalling anything on the tenant** (`uip eval ... delete`, `uip solution deploy uninstall`, `uip solution deploy delete`): name the target and confirm it with the user, unless the user already authorized that exact delete.
Expand Down Expand Up @@ -54,7 +54,8 @@
| Run coded evaluations | Coded | [coded/quickstart.md](references/coded/quickstart.md) § Evaluate | `coded/lifecycle/evaluate.md` |
| Create or scaffold a new low-code agent project | Low-code | [lowcode/lowcode.md](references/lowcode/lowcode.md) § Quick Start | `lowcode/project-lifecycle.md`, `lowcode/agent-definition.md` |
| Edit `agent.json` (prompts, model, schemas, contentTokens, entry-points.json) | Low-code | [lowcode/lowcode.md](references/lowcode/lowcode.md) § Capability Registry | `lowcode/agent-definition.md` |
| Add a low-code tool (Orchestrator process — RPA / agent / API / agentic — or Integration Service) | Low-code | [lowcode/lowcode.md](references/lowcode/lowcode.md) § Capability Registry | `lowcode/capabilities/process/*`, `lowcode/capabilities/integration-service/*` |
| Add a low-code tool (Orchestrator process — RPA / agent / API / agentic / Maestro Flow — or Integration Service) | Low-code | [lowcode/lowcode.md](references/lowcode/lowcode.md) § Capability Registry | `lowcode/capabilities/process/*`, `lowcode/capabilities/integration-service/*` |
| Use a Maestro Flow as a tool of a low-code agent (`type: "flow"`) | Low-code | [lowcode/capabilities/process/process.md](references/lowcode/capabilities/process/process.md) § Maestro Flow as a Tool | `lowcode/capabilities/inline-in-flow/inline-in-flow.md` for the `uipath.agent.resource.tool.flow.<release-key>` node on an inline agent |
| Add a client-side tool (conversational only — executes on the client surface, not the server) to a low-code agent | Low-code | [lowcode/lowcode.md](references/lowcode/lowcode.md) § Capability Registry | `lowcode/capabilities/client-side-tools/client-side-tools.md` |
| Add an MCP (Model Context Protocol) server tool to a low-code agent | Low-code | [lowcode/lowcode.md](references/lowcode/lowcode.md) § Capability Registry | `lowcode/capabilities/mcp/mcp.md` |
| Accept files as agent input / call the Analyze Files built-in tool | Low-code | [lowcode/capabilities/built-in-tools/built-in-tools.md](references/lowcode/capabilities/built-in-tools/built-in-tools.md) | `lowcode/capabilities/built-in-tools/analyze-attachments.md`, `lowcode/agent-definition.md` § File Attachments |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Built-in tools are pre-built agent tools that ship with the platform. They share a wire shape (`$resourceType: "tool"`, `type: "internal"`) and a fixed input/output schema per tool. Unlike process or Integration Service tools, built-in tools are self-contained at the agent level — no solution-level files, no `uip solution resources refresh`.

For process tools (RPA / agent / API / agentic), see [../process/process.md](../process/process.md). For Integration Service tools, see [../integration-service/integration-service.md](../integration-service/integration-service.md).
For process tools (RPA / agent / API / agentic / Maestro Flow), see [../process/process.md](../process/process.md). For Integration Service tools, see [../integration-service/integration-service.md](../integration-service/integration-service.md).

## When to Use

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ uip agent tool list --output json
For each tool name you plan to put in `matchNames`:
- **Found in `Data`** — proceed.
- **Not found** — **STOP.** Do not add the guardrail yet. Add the tool first, then return here:
- Process tool — RPA / agent / API / agentic, local or external: [../process/process.md](../process/process.md)
- Process tool — RPA / agent / API / agentic / Maestro Flow, local or external: [../process/process.md](../process/process.md)
- Integration Service tool: [../integration-service/integration-service.md](../integration-service/integration-service.md)

> `uip agent validate` enforces this: it fails with an error if a Tool-scoped guardrail references a tool that has not been added to the agent.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ Inline-agent resources — `tool`, `context`, `escalation` — share one path co
`<RES_UUID>` is a fresh UUID. It MUST match (a) the resource node's `inputs.source` in the flow and (b) the `id` field inside `resource.json`. The resource directory name is the UUID — never the human-readable resource name. Human-readable folder names are the standalone-agent convention; inline agents always use UUIDs.

Resource body shape is identical to the standalone-agent docs — only the folder name differs:
- Tools (`process` / `agent` / `api` / `processOrchestration`): [../process/process.md](../process/process.md) § Subtypes and § Tool resource.json Shape. Discovery is identical (`uip solution resources list` + `uip solution resources get`); subtype is selected by the `type` field.
- Tools (`process` / `agent` / `api` / `processOrchestration` / `flow`): [../process/process.md](../process/process.md) § Subtypes and § Tool resource.json Shape. Discovery is identical (`uip solution resources list` + `uip solution resources get`); subtype is selected by the `type` field.
- Context index: [../context/index.md](../context/index.md) § Agent-Level Resource Shape.
- Escalation: [../escalation/escalation.md](../escalation/escalation.md) § Agent-Level Resource.

Expand Down Expand Up @@ -252,7 +252,7 @@ Resource body shape is identical to the standalone-agent docs — only the folde
- `definitions[]` — The `uipath.agent.autonomous` definition copied from the flow registry supplies `model.serviceType: "Orchestrator.StartInlineAgentJob"`, BPMN type, version, and context. Do not copy those fields into the node instance.
- No node instance `model` block — the inline-agent source lives at `inputs.source`.

Resource nodes use the same `inputs.source` pattern as the autonomous agent — no instance `model` block. The `type` follows the per-kind patterns in § Resource nodes below — `uipath.agent.resource.tool.{process|agent|api|processorchestration}.<release-key>`, where `<release-key>` is the resource's release-key GUID returned by `uip solution resources list`:
Resource nodes use the same `inputs.source` pattern as the autonomous agent — no instance `model` block. The `type` follows the per-kind patterns in § Resource nodes below — `uipath.agent.resource.tool.{process|agent|api|processorchestration|flow}.<release-key>`, where `<release-key>` is the resource's release-key GUID returned by `uip solution resources list`:

```jsonc
{
Expand Down Expand Up @@ -294,14 +294,15 @@ Resources are separate canvas nodes wired to the agent via artifact handle edges
| RPA process | `uipath.agent.resource.tool.process.<release-key>` |
| Agent-as-tool | `uipath.agent.resource.tool.agent.<release-key>` |
| API workflow | `uipath.agent.resource.tool.api.<release-key>` |
| Maestro Flow | `uipath.agent.resource.tool.flow.<release-key>` |
| Process Orchestration | `uipath.agent.resource.tool.processorchestration.<release-key>` |
| Built-in tool | `uipath.agent.resource.tool.builtin.<tool-name>` |
| IS connector | `uipath.agent.resource.tool.connector` |
| Semantic index | `uipath.agent.resource.context.index.<index-name>.<index-id>` |
| Escalation | `uipath.agent.resource.escalation.<variant>` (e.g. `.coded-action-app`; discover with `uip maestro flow registry search "escalation"`) |
| Memory space | `uipath.agent.resource.memory.*` canvas node, backed by `features/<FeatureName>/feature.json` from `uip agent memory` |

`<release-key>` is the resource's release-key GUID from `uip solution resources list` (the row's `Key` field). The four process-tool kinds share the same registry-discovery flow and the same `resource.json` shape — only the prefix in front of `<release-key>` and the `type` field in `resource.json` differ. See [../process/process.md](../process/process.md) § Subtypes.
`<release-key>` is the resource's release-key GUID from `uip solution resources list` (the row's `Key` field). The five process-tool kinds share the same registry-discovery flow and the same `resource.json` shape — only the prefix in front of `<release-key>` and the `type` field in `resource.json` differ. See [../process/process.md](../process/process.md) § Subtypes.

## Walkthrough — End-to-End

Expand Down Expand Up @@ -372,6 +373,7 @@ uipath.agent.autonomous ← Inline agent
uipath.agent.resource.tool.process.<release-key> ← Tool: RPA process
uipath.agent.resource.tool.agent.<release-key> ← Tool: agent
uipath.agent.resource.tool.api.<release-key> ← Tool: API workflow
uipath.agent.resource.tool.flow.<release-key> ← Tool: Maestro Flow
uipath.agent.resource.tool.processorchestration.<release-key> ← Tool: process orchestration
uipath.agent.resource.tool.connector ← Tool: IS connector
uipath.agent.resource.tool.builtin.<tool-name> ← Tool: built-in
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Walkthrough for adding a tool that calls an Integration Service connector activity (e.g., Slack Send Message, Web Search, Jira Create Issue). Integration Service tools connect to external apps via pre-built connectors and authenticated connections.

For Orchestrator process tools (RPA / agent / API / agentic process), see [../process/process.md](../process/process.md).
For Orchestrator process tools (RPA / agent / API / agentic process / Maestro Flow), see [../process/process.md](../process/process.md).

## When to Use

Expand Down
Loading
Loading