Skip to content

feat(uipath-agents): Maestro Flow as a low-code agent tool - #4751

Open
ionut-mihalache-uipath wants to merge 1 commit into
mainfrom
docs/agents-flow-tool
Open

ionut-mihalache-uipath wants to merge 1 commit into
mainfrom
docs/agents-flow-tool

Conversation

@ionut-mihalache-uipath

Copy link
Copy Markdown

What

Documents type: "flow" — a Maestro Flow used as a tool of a low-code agent — in the uipath-agents skill. The skill listed four process-tool subtypes and had nothing on Flows, so an agent asked to use one had no contract to follow.

Changes

  • capabilities/process/process.md: flow in the Subtypes table and every other subtype list, plus a Maestro Flow as a Tool section covering what uip solution resources list returns for a deployed Flow and for a Flow project in the same solution, where the input/output contract comes from in each case, and what uip solution resources refresh writes.
  • Registry and routing rows (SKILL.md, lowcode.md), the subtype lists in the sibling references, and the uipath.agent.resource.tool.flow.<release-key> node type in inline-in-flow.md.
  • New integration task tests/tasks/uipath-agents/lowcode/solution_flow_tool/, with a fixture solution that holds a Flow project.

Decisions a reviewer cannot get from the diff

  • type is lowercase "flow". A deployed Flow is listed with Type: "Flow"; copying that verbatim fails uip agent validate with Invalid input.
  • A Flow project in the same solution exposes no schema through resources get. Its contract is read from the Flow's variables: in variables bound to the start trigger are inputs, out variables are outputs, inout variables are in neither. That mirrors how the Flow is packed, and the fixture carries an inout variable so the checker guards it.
  • Agent Builder offers Flows in its tool picker only on tenants where the Flow tool is enabled. The doc says so without naming a flag, as the skill does elsewhere.

Verification

Ran:

  • The documented resource.json through uip agent refresh and uip agent validate (uip 1.205.0); the binding is process with subType flow.
  • uip solution resources list / get / refresh for a deployed Flow and for a local Flow project, to take the documented field names and output paths from real output.
  • The task's checker against a project authored by following the doc.
  • npm run skills:validate, skills:check-links, scripts/check-sensitive-content.py, scripts/check-skill-status.py: pass.
  • npm run skills:test: 471 pass, 1 fail. The failure is the built studioweb flavor mentions no new command the browser bundle cannot run (uipath-coded-apps), which fails the same way on an untouched main.

Not run:

  • coder-eval on the new task, so there is no passing-run claim yet.
  • skill-lint (not available locally).
  • No agent was run end to end calling a Flow.

🤖 Generated with Claude Code

https://claude.ai/code/session_0136ibA39NTYe4XHq5Z2Ch32

The agents skill documented four process-tool subtypes and had nothing on
`type: "flow"`, so an agent asked to use a Maestro Flow as a tool had no
contract to follow.

- process.md: `flow` in the Subtypes table and every other subtype list, plus
  a "Maestro Flow as a Tool" section: what `uip solution resources list`
  returns for a deployed Flow and for a Flow project in the same solution,
  where the input/output contract comes from in each case, and what
  `uip solution resources refresh` writes.
- A local Flow project exposes no schema through `resources get`; the
  contract is read from its variables: `in` variables bound to the start
  trigger are inputs, `out` variables are outputs, `inout` is neither.
- Registry and routing rows, the subtype lists in the sibling references, and
  the `uipath.agent.resource.tool.flow.<release-key>` node type for inline
  agents.
- New integration task `solution_flow_tool` with a fixture solution holding a
  Flow project.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136ibA39NTYe4XHq5Z2Ch32
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @ionut-mihalache-uipath's task in 45s —— View job


Coder-eval task lint (advisory)

1 task YAML changed. Verdicts: 0 Critical, 0 High, 0 Medium, 0 Low, 1 OK. There is also one PR-level High: no claim of a passing run.

Rubric: .claude/commands/lint-task.md. This check is advisory and never blocks merge.

Evidence of passing run

  • ❌ High — The PR body does not claim the new task has been run and passed. It says the opposite: "Not run: coder-eval on the new task, so there is no passing-run claim yet." Running the checker against a project written by hand from the doc does not count as a task run. Please run the task and edit the PR description to add a line like: Ran skill-agent-solution-flow-tool locally and it passed.

Per-task lint

tests/tasks/uipath-agents/lowcode/solution_flow_tool/solution_flow_tool.yaml — verdict: OK

  • Prompt over-specification: none found. The prompt (L29–37) gives the goal and names the fixtures it grades against. It does not mention type: "flow", the variables, or any CLI verbs.
  • Meaningful coverage: strong. The main check is check_solution_flow_tool.py (L117–123, weight 6.0). It compares type == "flow" exactly, so "Flow" fails, and it checks location, folderPath and processName. It also requires referenceKey to match the fixture's process/flow/OrderFlow.json, and requires the input and output schemas to be exactly {orderId} and {status}, which keeps the inout variable retryCount out of both. The .uipx length(Projects) >= 2 check covers registration.
  • Could pass for the wrong reason: no gating weakness. The expected values come from the fixture, not the prompt, so a lazy agent cannot guess them. The solution resources list pattern (L60) has an unbounded .* before --source\s+local, but it is informational (pass_threshold: 0.0). Optionally tighten it to [^;&|\n]*.
  • Near-duplicate: not raised. The task reuses the scaffold of solution_maestro_tool.yaml, but it tests a different operation: a lowercase flow type, plus schemas derived from the Flow's in/out variables.
  • CLI verb reachability: agent refresh, agent validate, maestro flow init, maestro flow variables list, solution init and solution resources list are all in assets/uip-catalog-snapshot.json. I checked this by hand because running scripts/check-cli-verbs.py was not permitted in this runner.
  • Validate-only flow tests: does not apply, because the skill tag is uipath-agents, not a flow-building skill.
  • Sandbox / run limits: no @uipath/cli in env_packages, and the run limits are under run_limits:.

Within-PR duplicates

  • No duplicate clusters detected. Only one task was added.

Conclusion

  • ⚠ The task itself passes the rubric. The only issue is the missing passing-run claim (High). Advisory only — not blocking merge.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @ionut-mihalache-uipath's task in 1m 27s —— View job


Summary

Adds type: "flow" (a Maestro Flow used as a low-code agent tool) to uipath-agents. It adds a new Maestro Flow as a Tool section in process.md, extends the subtype lists and routing rows in the sibling references, adds the uipath.agent.resource.tool.flow.<release-key> inline node type, and adds a new brownfield integration task with a Flow-project fixture. The change is well scoped and nothing blocks merge. The main gap is the missing passing coder-eval run, plus two small spec and test-tightening points.

Change-by-Change Review

1. references/lowcode/capabilities/process/process.md

Low

  • The two-column Deployed vs. Local table (process.md:312-317) works well. The variable → schema mapping table and the lowercase-flow rule give the agent an exact contract.
  • The new Kind row (:65) and the fix to the multi-agent example (:285, Kind "process" case-insensitive) correct a real casing mismatch that was already there. Good catch.
  • Type mapping is only partly specified (:331-336). Only Type: "file" gets an explicit JSON Schema mapping. "with its Type and Description" doesn't say how Flow variable types such as number, boolean, object and array (or any nested item/property schema) map, or whether required should be set. The existing Copy the process schema exactly rule says "do not add required", but a Flow variable has no required to copy from, so the agent has to guess. Fix: add one sentence: "Flow scalar Type values are JSON Schema types; copy them as type. Do not add required." Add the object/array nesting rule if the CLI exposes one. Fix this →
  • Delegating Flow edits to uipath-maestro-flow (:321) and using the uip maestro flow variables list verb read-only is allowed under the self-containment rule. The verb is in assets/uip-catalog-snapshot.json. OK

2. SKILL.md, lowcode.md routing rows

Low. Each file now has two rows that route Flow requests to the same process.md: the widened "Add a low-code tool / process tool" row plus a dedicated type: "flow" row. This is acceptable because the dedicated row deep-links to the section, but it is mild duplication. You could keep only the dedicated row and leave the generic row unchanged. Frontmatter is untouched.

3. inline-in-flow.md, solution-files.md, solution-resources.md, project-lifecycle.md, built-in-tools.md, guardrails.md, integration-service.md

OK. These are list and table extensions, and they are consistent with each other (Flow on remote rows, flow on local rows, process/flow/ directory). The "four → five process-tool kinds" count is updated. The solution-files.md note that refresh generates the files and there is no hand-authoring template is clear.

None of the edited passages sit inside a skill-flavor block. The studioweb overrides for lowcode.md, project-lifecycle.md and inline-in-flow.md replace other blocks only, so the studioweb flavor inherits these edits.

4. tests/tasks/uipath-agents/lowcode/solution_flow_tool/

Medium (no passing run). The task is otherwise well built:

  • task_id, required tags (uipath-agents, integration, mode:build) and the vocabulary (lifecycle:generate, low-code) match the sibling solution_* tasks.
  • The prompt is minimal and does not hand-hold.
  • Gating is outcome-based. Discovery checks are advisory (pass_threshold: 0), and there is no gating --output json check.
  • The inout retryCount fixture variable guards the "neither schema" rule, and the checker gives targeted error messages for "Flow" and processOrchestration.

Issues:

  • No coder-eval passing-run claim (the PR body states this). .claude/rules/test-writing.md step 5 requires one, and /lint-task flags its absence as High. Run it before merge.
  • Low: assert_schemas (check_solution_flow_tool.py:172-188) compares property names only. An agent that writes orderId as {} or as number still passes. Fix: also assert inputSchema.properties.orderId.type == "string" and outputSchema.properties.status.type == "string". Fix this →

What's Missing

  • A passing coder-eval run claim for skill-agent-solution-flow-tool.
  • Nothing tests the deployed-Flow path (Source: "Remote", Type: "Flow" → "flow"), even though it is the headline gotcha (Flow rule 1). Sibling subtypes have external_*_tool tasks. Add external_flow_tool if a test tenant can host a deployed Flow; otherwise state in the PR that it is deferred.
  • No change to CODEOWNERS, skill-status.json or skills.sh.json is needed, because no skill folder was added or renamed.

Area Ratings

Area Status Notes
Frontmatter OK Unchanged
E2E Tests Issue New integration task looks sound, but there is no passing-run claim and no deployed-Flow task
Skill Body OK Routing rows are slightly redundant (Low)
References & Assets OK Flow type mapping is only partly specified (Low). All links and anchors resolve (agent-definition.md#file-attachments-job-attachment, #maestro-flow-as-a-tool)
Repo Hygiene OK No secrets or personal paths. Fixture GUIDs are synthetic. Scoped to uipath-agents

Issues for Manual Review

  • Whether the canvas node type uipath.agent.resource.tool.flow.<release-key> matches what the Flow registry emits. The PR verified the agent-level resource.json, but not an inline agent wired to a Flow tool.
  • Whether uip maestro flow variables list returns Direction / TriggerNodeId / Type in PascalCase, as the doc assumes, for the fixture's camelCase variables.globals.
  • Whether the "Deployed Flow" entry-point note (process.md:319, which says top-level InputArgumentsSchemaV2 describes EntryPointName, not inline-agent entries) holds for Flows that have several triggers.

Conclusion

Approve once a coder-eval run passes. The documentation is accurate as far as this review can check, consistent across files, and flavor-safe. The type-mapping sentence and the stricter schema assertions are optional improvements.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant