Repository navigation
Conversation
…s, then author it with connector() Short version: an external agent or automation the connector library lacks no longer pushes the flow out of the SDK loop. `uip maestro registry prepare <key> --action <op>` builds its entry from the tenant's node and the object's request fields, and `connector(...)` authors it. This replaces the `nodes create` + `configure --detail` fallback in external-agent.md. Merge after the SDK release that ships UiPath/builder-sdk#1988's PR: that release writes the agent's execution type on the compiled node. 🤖 Generated with Claude Code Co-Authored-By: [Claude](mailto:noreply@anthropic.com)
|
Claude finished @tmatup's task in 49s —— View job SummarySwaps the "not in the library" path in Change-by-Change Review1.
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | OK | Unchanged |
| E2E Tests | Issue | No task covers the external-agent prepare path |
| Skill Body | OK | Router row is consistent |
| References & Assets | Issue | Wrong import path; example contradicts the lookup rule |
| Repo Hygiene | OK | Scoped to one skill; flavor block boundaries intact; no secrets or personal paths |
Issues for Manual Review
- Whether
prepareactually works for a Curated agent operation that isn't in the library. The old text implied it didn't, which is why it fell back to the CLI. The PR says this was verified on alpha via builder-sdk#2051. - Whether
uipath-salesforce-agentandexecute-salesforce-agentare the real connector key and action names. - Whether the "If
preparewarns … runuip update" fallback matches what the CLI prints.
Conclusion
Request changes. Fix the import path in #1 and the example in #2 before merging. Once those are fixed, the approach is sound: it keeps the flow in the SDK loop and drops the "no SDK source" restriction. Merge only after the SDK release that ships builder-sdk#2051, as the title says.
…ow-sdk/, and author agent_id as a lookup 🤖 Generated with Claude Code Co-Authored-By: [Claude](mailto:noreply@anthropic.com)
|
Addressed the Claude review in the latest commit:
🤖 Generated with Claude Code |
Merge after the SDK release that ships UiPath/builder-sdk#2051.
Short version
An external agent or automation that the connector library lacks no longer pushes the flow out of the SDK loop. Before,
references/external-agent.mdsent the agent tonodes create+configure --detailJSON by hand and told it to drop the flow's SDK source. Now it runsuip maestro registry prepare <key> --action <op>and authors the step withconnector(...), like any library operation.Example (Salesforce Agentforce, not in the library):
What changed
references/external-agent.md: theexternal-agent-cliblock now covers prepare, the import, required inputs, theagent_idlookup, and the execution type (compile writesinputs.detail.executionType, asnodes configuredoes).SKILL.md: the node-type row says to prepare the operation instead of using the CLI.Why it waits for the release
prepare+connector()works on current SDK releases. builder-sdk#2051 adds the execution type to the compiled node. Without it, a sync agent runs under the registry's async service type. That PR also verified the whole path on alpha (prepare, compile,flow validate: Valid).Checks
npm run skills:validateOK (default and studioweb).scripts/check-skill-links.mjs: all links and anchors resolve.git diff --checkclean.Refs UiPath/builder-sdk#1988
🤖 Generated with Claude Code
Co-Authored-By: Claude