Use a capability to improve one step
The Orbit implementation needed responsive layout and visible keyboard focus. In the recorded execution, the native Agent discovered and read an installed UI design Skill and used its search guidance before editing the page. The result was actual CSS plus checks, not merely a Skill listed in Settings.
This was native Agent discovery. It is not evidence that the user selected a / token or that a Rovai Toolbox workflow ran. The independent review still found a contrast issue, which shows why a selected capability is not a quality certificate.
Request an available native Skill
- Inspect Settings → Skills for the teammate’s Agent. Read the capability’s purpose and confirm that the required native installation exists. This screen does not install or edit it.
- Return to the project conversation, choose the intended teammate, type / and select an available Skill candidate. The candidate may come from the Agent’s user or project scope.
- Describe the desired result and file limits beside the selected token. Send the request.
- Look for an actual Skill read or related tool step in Run, and inspect the delivered files. A token establishes the request; execution evidence establishes what happened.
An example request after selecting a design Skill
Use the selected Skill to improve the Orbit page’s narrow-screen layout and visible keyboard focus. Preserve the three existing fixture links and demo labels. Change only index.html and styles.css, then report the checks actually completed.
Assign a Toolbox capability separately
Settings → Toolbox contains Rovai collaboration instructions such as review-duo. Open the item, read its instructions and choose the teammates who should receive it. This persistent assignment differs from selecting a native Skill for one message.
An assigned instruction can guide a teammate’s working method, but it does not independently trigger a Run, create approvals or grant new filesystem rights. Send a real request and inspect how the Agent uses it.
How to use it
- Open Settings → Skills, choose an Agent, and read the native Skills it exposes. This page is for inspection.
- Open Settings → Toolbox to read a built-in tool’s instructions and select the teammates who should receive it.
- For a single request, type / in the conversation composer and choose an available Skill from the picker before sending.
Three ways Skills appear
- Settings → Skills
- Select an Agent to inspect the native Skills it exposes and read their descriptions. This page is an inventory, not a Skill editor.
- Settings → Toolbox
- Read a built-in collaboration tool’s instructions and assign the teammates who should receive it.
- Composer / picker
- Type / in a conversation and choose an available Skill for this request. The selection appears as a structured draft token.
When to use which entry
Use the Skills inventory to learn what the selected Agent already knows how to do. Use Toolbox for durable teammate assignment. Use the composer picker to call attention to one Skill in a specific message.
After sending, inspect the execution and result. Choosing a Skill is a request to the Agent, not a guarantee that every instruction in that Skill was followed.