Publish, install, review, and share skills and routines in Delegate and Cartographer, including permissions and how feeds work.

A skill you build lives only on your machine until you publish it. Since a routine is a skill marked user-invocable, everything on this page applies to routines too.

Publishing a skill uploads it to a feed — a place a skill package can be read from and written to. You switch between feeds with the source selector in Discover skills:

See Skills reference for the Skills, Discover skills, and Review queue views these feeds populate.

Whether you describe it to the agent or write it by hand, a skill needs:

These become the skill's Overview and When to use fields when you publish it.

You can also turn something you did in a chat into a reusable skill by asking for it directly, by using the suggested prompt Turn my current task into a reusable automation skill, or by selecting Create recording to capture the steps by performing them yourself.

Either way, the result is a skill folder on your machine — nobody else can see it until you publish it. Find it under Add-ons & Integrations → Skills → Discover skills, listed under Installed as Not published.

In Add-ons & Integrations → Skills, select Add skill and choose one of three options:

Three things need to be true, or publishing won't work:

Two separate permission layers apply here, and they control different things:

Holding Libraries.Create only means Orchestrator lets you publish — it says nothing about what the skill itself is allowed to do at runtime. That's controlled entirely by Tool permissions and your Approval mode, the same as any other action Delegate takes.

Before installing a skill you didn't build yourself, check its Files tab for what tools, connections, and file system or network access it uses, and whether that matches its stated purpose. Be cautious of a skill that asks for tools unrelated to its purpose, broad file system access without justification, or a connection to a sensitive service (banking, HR systems) it has no obvious reason to need.

In terms of roles, Automation User is enough to browse, install, and run skills. Publishing needs a role carrying Libraries.Create, typically Automation Publisher or a custom tenant role.

To publish a skill you built, take the following steps:

Your Role and Type choices become properties on the resulting package, your tags become labels, and your Overview becomes its description.

To confirm it published, check the detail page: a tenant name now appears next to the version, and the action changes from Publish local changes to Republish. For a definitive answer, check Tenant → Packages → Libraries → Tenant in Orchestrator — this is the actual package listing.

Once your skill is published, your team can find it under Available in Discover skills and select Install to download it into their own skills folder. It's ready for the agent to use starting with their next conversation. Refer to Installing a skill.

Edit the skill — in a chat, or by changing its files directly. There's no in-place edit of a published version; every change ships as a new version. Once you've made a change:

Versions only ever go forward — reusing a version number is rejected.

A skill you're publishing for others is more useful — and more likely to be trusted — when it meets these criteria:

To install a skill someone else has published, take the following steps:

Installing, enabling, or disabling a skill only takes effect in new conversations. When a newer version is published, the card shows Update available. If you've edited your own copy, updating warns you first and offers to keep your changes or overwrite them.

To remove your own copy without affecting the published package, use Uninstall from this device. To remove the package entirely — for everyone — use Delete from Orchestrator from the same menu; see Publishing a skill.

If you don't hold the Libraries.Create permission, the publish form offers only Submit for review. Fill in the same fields as a normal publish and submit — nothing goes live yet.

Track your submission from Add-ons & Integrations → Skills → Review queue, under My submissions. It moves through a few states:

If you hold the publish permission, a second lane in the Review queue shows submissions waiting on you. Opening one gives you version, submitter, description, and where it will land.

Everything above is also available by asking, in your own words:

Use the chat route when you're already in one, want it done in one sentence, or are surveying many skills at once. Use the Discover skills UI when you want to review or edit every field before it goes out, need Submit for review (the chat route publishes directly), or want Generate with AI to draft a description.

A shared feed is what lets a skill reach other organizations, not just your own tenant. Shared feeds are configured by UiPath at deploy time, not self-service — if your organization doesn't have one, you won't see any of this, and publishing and installing within your own tenant work exactly as described above.

If your organization has a shared feed configured, the publish form grows a Share to feed section with a checkbox per feed alongside your own tenant. Check the boxes before publishing — whichever are selected, your skill goes there too.

Publishing to several destinations at once can partly succeed. Delegate reports exactly which ones failed — for example, "Published to org. Could not publish to: <feed>." Whichever destinations did succeed stay published.

Someone in another organization who receives your skill through a shared feed can:

None of these options installs the skill directly from another organization's feed. The receiving organization always decides — either an admin brings a copy in under their own governance, or someone tries it out first without installing anything at all.

The trash icon's menu on the skill details page has two actions with two different outcomes:

Uninstalling asks for confirmation first: "Are you sure you want to uninstall '<skill>'? This will remove it from your local machine."