docs(uipath-platform): personal workspace upload creates a process, file arguments take attachment references - #3787

Claude finished @danmunteanu1's task in 1m 26s —— View job

PR Review: docs(uipath-platform) — personal workspace upload & attachment references

• Read review criteria and project conventions
• Read full diff
• Read full changed file for context
• Check skill-specific rules (links, cross-references, secrets)
• Post review findings

Summary

Adds two pieces of operational knowledge to run-jobs.md discovered while running automations from genomes: (1) uploading to a personal workspace feed auto-creates a process, and (2) --attachment does not fill a file argument — the caller must pass an attachment reference JSON in --input-arguments.

Change-by-Change Review

1. skills/uipath-platform/references/orchestrator/run-jobs.md — personal workspace note (line 43)

Severity: OK

The new paragraph is well-placed between Steps 1 and 2, exactly where an agent needs the warning before it blindly runs processes create. Prescriptive phrasing ("Look for it with processes list before Step 3") follows content-quality rules. Clean.

2. skills/uipath-platform/references/orchestrator/run-jobs.md — attachment reference pattern (line 188)

Severity: Low

The appended sentence is technically correct and uses proper <UPPER_SNAKE_CASE> placeholders. The attachment reference JSON pattern ({"<ARGUMENT>": {"ID": "<ATTACHMENT_ID>", "FullName": "<FILE_NAME>"}}) gives the agent exactly the shape it needs.

Minor observation: the --attachment bullet is now ~440 characters of dense single-line prose. It's still readable, and splitting it would break the established list structure, so this is fine as-is. No action needed.

What's Missing

Nothing identified.

Area Ratings

Issues for Manual Review

• Attachment reference JSON shape — the {"<ARGUMENT>": {"ID": "<ATTACHMENT_ID>", "FullName": "<FILE_NAME>"}} pattern is domain knowledge from running genomes. Reviewer should confirm this matches the Orchestrator API's expected format for file-argument attachment references.

Conclusion

Clean PR. Two small, high-signal additions that prevent real agent mistakes (duplicate process creation and misuse of --attachment for file arguments). Approve.