Tools and Skills — rebyte.ai docs

Tools and Skills are part of the Agent definition. A Response cannot add or replace them at request time.

Internal tools

{"kind":"internal","name":"web_search_&_browse"}

Supported internal names:

web_search_&_browse
sandbox
skills
coding_agent
ask_user_question
report_builder
company
app_builder_contract
github
sound_studio
speech_generator
http_client

When mcpServers is omitted, a new Agent receives these seven tools:

web_search_&_browse
sandbox
skills
coding_agent
ask_user_question
report_builder
company

Pass an explicit mcpServers array to replace that initial set.

Composio toolkits

{"kind":"composio","toolkit":"github"}

toolkit is the canonical Composio toolkit name, up to 300 characters.

Custom MCP servers

{"kind":"custom","serverId":"550e8400-e29b-41d4-a716-446655440000"}

serverId is the UUID of an MCP server already owned by the organization.

Credentials and connection grants are stored separately in Rebyte. Do not put secrets in an Agent definition or agent.toml.

Skills

A Skill points to the repository directory containing SKILL.md:

{"repo":"owner/repository","path":"skills/research"}

Rules:

repo uses canonical owner/repository form without a .git suffix.
path is a canonical repository-relative directory.
path points to the directory, not to SKILL.md itself.
The pair of repo and path must be unique within the Agent.

The skills internal tool must be present for the Agent to invoke configured Skills.

Execution events

Text and MCP calls use Responses events. Rebyte also emits additive tool progress events, including action-required and failure states. See Responses streaming.

If ask_user_question blocks a run for an answer, use the lower-level Message answer endpoint.