Contribute in GitHub:
Edit online
copyright: year: 2024 last updated: 2024-06-07
Getting started as a builder
Builders are responsible for creating customized skills that fit their organization's needs. As a builder, your focus is mostly on building and testing skills to implement them as team skills with a specific set of aptitudes for use by everyone in your team. You can build these custom skills through discovery apps or by using OpenAPI specifications.
Skills for builders
To you as a builder, skills complete tasks as a result of the interpretation of intent that you feed into Orchestrate. A skill can be as simple or complex as it needs to be by completing a single task or to connecting several tasks together. When you craft a skill, you provide everything, from the API endpoint to the rules that dictate how a user can use a skill. At the end, your user sees this entirely as a single skill execution.
The following are your tasks in defining and implementing a skill:
➤ Building skills into Orchestrate
➤ Ensuring that the UI content of your skill is clear and concise
➤ Testing and deploying your skill
Extend your builder skills with assistants and automations
Extend your skills as a builder by combining the robustness of automations and assistants to your digital worker.
Create assistants to combine generative AI and conversational AI features to tackle complex integrations and workflows and deliver powerful conversational experiences. For more information, see Building assistants.
Other considerations
If you are accessing Orchestrate for the first time, see Getting your first access to IBM watsonx Orchestrate.
As a builder, you have permission to do everything that users can do. For more information, Getting started as a user.
Parent topic: