skills: Instructions file for Claude Code

UiPath Agent Skills — Project Rules

This repository contains self-contained AI agent skills for UiPath automation development. Skills are installed as a Claude Code plugin and teach AI agents how to build, run, test, and deploy UiPath automations.

Architecture

• Skills are self-contained. Each skill under skills/ must function on its own: it MUST NOT import, inline, or read another skill's files, and MUST still deliver its core value if sibling skills are absent. A skill MAY delegate a task to a sibling skill in this same plugin at runtime (e.g., spawn a subagent that hands an artifact edit to the artifact's owning domain skill) when that work is the sibling's domain — provided the delegation degrades gracefully (the skill still presents an actionable result when the sibling is unavailable).
• SKILL.md is the canonical default contract. Every skill folder must have a complete SKILL.md with valid YAML frontmatter. Local/default consumers can understand it without a flavor manifest or runtime resolver. Shared guidance stays there; only genuinely different passages may be enclosed by named flavor-block comments.
• Custom flavors inherit the complete catalog and contain only sparse exceptions. Every flavor ships every canonical skill. Files under skill-flavors/<flavor>/<skill>/ mirror canonical skill paths and contain only complete replacement blocks. If no override exists, the canonical file is intentionally reused unchanged. Do not duplicate a whole skill merely to change a few paragraphs.
• Build files before packages. Build complete default and custom-flavor skill trees, validate those final files, and only then stage packages. Consumers must copy a finished tree; they must not interpret flavor markers or compose Markdown at runtime.
• Session hooks are Node scripts or direct uip ingestion — never shell scripts. Telemetry ships NO script: hooks/hooks.json pipes the raw hook payload to uip track --hook, and the field derivation lives in the CLI (UiPath/cli track-hook.ts, guarded by its vitest suite). The remaining session hooks are each one hooks/<name>.mjs run by node. Both node and uip are native-executable entry points, so no shell dialect and no PowerShell execution policy applies, and both are present wherever the skills were installed through the Node-based uip CLI. Each hooks.json entry is a bash/PowerShell polyglot command whose both branches guard for the missing binary (silent exit 0) — telemetry's PowerShell branch resolves uip.cmd explicitly, never the bare uip (PowerShell would prefer npm's uip.ps1 shim, which execution policy can block). Do not add a shell field to these entries; the polyglot depends on Claude Code's default shell selection. Do NOT reintroduce .sh/.ps1 hook implementations: the retired PowerShell twins required an Authenticode signing gate at publish and still failed under Group-Policy execution policy.