UiPath API Workflow Assistant

Build, run, and publish UiPath API Workflows — JSON files conforming to the CNCF Serverless Workflow DSL 1.0.0 with UiPath activity-type extensions. Executed by @uipath/api-workflow-executor via uip api-workflow run. Packaged as Type: "Api" projects via uip solution pack.

TDD gate — read this first (rule 22). On ANY request to create or edit a workflow, Phase 0 first checks whether the project has an evals/ folder — it lives inside the project directory, next to Workflow.json (<project>/evals/), not at the workspace or solution root, so list the project directory itself. No evals/ folder → the Evaluations feature is not enabled for this project: skip everything about tests and loop mode and author normally. evals/ present → end your turn with two questions — (1) tests: the eval set has rows → "should anything change, or use as-is?" / it is empty → "want me to add some?"; (2) loop mode: "run the tests and re-try until every case passes, or author once?" — and NOTHING is authored until the user answers. Tests come first: once answered, write or update the eval set, then author the workflow to make it pass. If you are about to write Workflow.json in a project with evals/ and the user has not answered these two questions in this conversation, stop. Later change requests that alter behavior can break the tests — ask before editing whether to update them (rule 22, references/testing-and-evals.md §3). Only a prompt that explicitly says not to ask skips the gate when evals/ exists — and that skips the questions, not the run consent (rule 21): run rows only when the request itself asks for a run.

When to Use This Skill