Understanding Skill Execution Scope
When creating or editing a skill, you must define its execution scope to control where the skill can be invoked.
Scope Options
| Scope | Description |
|---|---|
| AOP execution | Skill can only be used within AOPs as part of a structured business process |
| Master orchestrator & AOP execution | Skill can be invoked directly by the Master Orchestrator for employee queries, and also used within AOPs |
AOP Execution Only
Use this scope when the skill:
- Is part of a multi-step business process
- Requires specific workflow context to function correctly
- Performs sensitive operations that need controlled execution
Example: A skill that updates employee records should only run within an approved HR process, not via ad-hoc queries.
Master Orchestrator & AOP Execution
Use this scope when the skill:
- Handles general employee queries
- Doesn't require workflow context
- Is safe for conversational invocation
- Can also be reused within AOPs
Example: A skill that looks up company holidays can answer employee questions directly and also be used within leave management AOPs.
Quick Decision Guide
| If the skill... | Choose |
|---|---|
| Handles standalone queries from employees | Master orchestrator & AOP |
| Requires approval workflows or specific context | AOP execution only |
| Performs sensitive data operations | AOP execution only |
| Is a general utility (search, lookup, notify) | AOP execution only |
How to Configure
- Navigate to AI Colleagues → Skills
- Click Create skill or edit an existing skill
- Complete Step 1: Skill details
- In Step 2: Execution scope, select where the skill can execute
- Click Create to save
Updated 2 days ago