Considerations for building, sharing, running, and deploying skills.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with the Einstein for Sales add-on. |
| User Permissions Needed | |
|---|---|
| To create, edit, run, and share your own skills in Skill Builder: |
AI Skill User permission set
|
| To create, edit, run, and share all skills in Skill Builder: |
AI Skill Manager permission set
|
Build and test
- Start with a simple skill: one task. Add agent actions after the instructions.
- Write a specific description so that natural-language matching can find the skill.
- In Guidelines, state what not to do, especially when agent actions change data.
- Make the skill available in Agentforce Coworker if it needs Coworker connections such as Slack or Google Drive.
- If a skill returns an inaccurate response, make the instructions more specific and add context. If the problem continues, then share the details with Salesforce Customer Support.
Share and run
- Skills are private by default until shared. Share access is Read only or Read and write.
- Sharing grants access. It doesn’t add the skill to My Skills.
- Assign the AI Skill User permission set so that users can run skills they can access.
- A skill appears in the slash-command list when it’s published, in My Skills, and the skill is configured to point to that target agent.
- Unpublish stops runs and removes the skill from My Skills.
Limits
- Skills run as the running user. Object permissions, field-level security, and sharing rules apply.
- Skills aren’t available on mobile.
- Multi-language instructions aren’t supported.
- Scheduled or event-driven skill runs aren’t supported.
- One skill doesn’t run another skill.
Versions
- To keep a snapshot, click Save as a New Version.
- The published version is the one that runs.
Deployment
- Skills deploy as metadata through Salesforce CLI, change sets, and unlocked packages.
- Retrieve returns one version: the published version, or the latest version if none is published.
- Deploy adds a version. It doesn’t overwrite existing versions.
- My Skills membership doesn’t deploy. Users in the destination org add skills from Browse.
- First-generation managed packages aren’t supported. Standard skills can’t be retrieved or packaged.