- Getting started
- Capabilities
- RPA workflows
- Task recordings
- Custom skills
- Operate
- Troubleshoot
- Data privacy and governance
- Product availability
- Earlier Autopilot capability sets
- User scenarios
- Prompting guide
- Example prompts
- Autopilot usage pool for testing
- Best practices and limitations
- Supported models and limits
- Quality-check requirements
- Generate tests for requirement
- Import manual test cases
- Find obsolete tests
- Generate tests for SAP transactions
- Generate synthetic test data
- Generate test reports
- Generate coded test cases
- Search Test Manager project
- Troubleshooting
- Troubleshooting
- Autopilot for Everyone
- About Autopilot for Everyone
- Licensing
- User types
- Data sources
- Toolset automations
- Localization
- Prerequisites
- Autopilot widget
- The Autopilot for Everyone tenant card
- Prerequisites for installation
- Enabling Anthropic models
- Installing Autopilot for Everyone
- Updating Autopilot for Everyone
- Uninstalling Autopilot for Everyone
- Configuring Autopilot for Everyone
- Disabling the Autopilot welcome screen in Assistant
- Configuring an LLM for Autopilot for Everyone
- Deploying toolset automations
- Prompt-to-response flow
- Launching Autopilot for Everyone
- Autopilot settings for business users
- Using a specialized Autopilot
- Using a starting prompt
- Uploading and analyzing files
- Running automations
- Interacting with Autopilot answers
- Using suggested prompts
- Starting a new chat
- Chat history
- Providing general feedback
- Clipboard AI Enterprise version
- Designing relevant automations for Autopilot for Everyone
- Troubleshooting
Custom skills
Add your own skills to Autopilot in Studio Desktop, Studio Web, and VS Code, for one project or for all projects on your machine, by importing a skill file, writing one, or asking Autopilot to write it.
Add custom skills to extend Autopilot with your own instructions and standards. A custom skill is a SKILL.md file, or a .zip file that contains one.
In Studio Desktop, Studio Web, and VS Code, you can add a custom skill to a project. In Studio Desktop and VS Code, you can also add one to all projects on your machine.
Each user adds their own custom skills. Autopilot doesn't distribute custom skills across an organization.
Prerequisites
- The
SKILL.mdfile has anameand adescriptionin its frontmatter. Autopilot doesn't import a skill without a description. - The skill name differs from the UiPath skill names. Don't use a name that starts with
uipath-. UiPath skill updates keep your custom skills only when their names differ from the UiPath ones. - In Studio Desktop, a project is open.
Adding a skill to a project
- In the Autopilot panel, select Settings.
- Select the Skills tab.
- Add the skill:
- To import a skill file, select Import, then select a
.ziporSKILL.mdfile. If a skill with the same name exists, select Replace to overwrite it. - To write a skill, select New skill, enter the Name, Description, and Content, then save the skill.
- To import a skill file, select Import, then select a
The skill appears under Your skills and is switched on.
You can also describe the skill in the chat and ask Autopilot to write it for you.
In Studio Desktop and VS Code, project skills are stored in the <project>\.local\autopilot\skills folder. This folder is not shared through source control, so teammates who open the same project don't get your skills.
Adding a skill for all projects on your machine
In Studio Desktop and VS Code, add a skill to every project on your machine:
- Create a folder for the skill.
- Add the
SKILL.mdfile to the folder. - Copy the folder to the user-level skills folder:
- Windows:
%USERPROFILE%\.autopilot\skills - macOS:
~/.autopilot/skills
- Windows:
In Studio Desktop, on the Skills tab, the skill appears under Built-in skills. You can't edit or delete it from the Settings menu. If a project skill has the same name, Autopilot uses the skill from the user-level folder.