Tools Studio and tool profiles

Tools Studio defines capability profiles used by the main coordinator and background agents. A profile combines an allowed tool catalog, routing guidance, skill files, and approval policy.

Tool profiles

Select an existing profile or create one for a bounded role such as web research, scheduling, or coding. Give it a description that explains what work belongs there.

Use exact tool names or supported prefix selectors. A tool not included in the profile is absent from that agent’s callable schema; prompt instructions cannot restore it.

Follow least privilege

• Give research profiles read and browser tools, not deployment tools.
• Give coding profiles access only to the selected workspace.
• Keep outbound messaging and destructive writes behind approval.
• Separate specialized profiles instead of building one universal profile.

Marketplace connectors also enforce their own channel, repository, project, or object allowlists. Use both layers.

Skill files

Skill Files (optional) attach focused knowledge and working instructions to a profile. Search the known catalog, select relevant files, or create a Markdown skill under the allowed knowledge root.

Keep a skill narrowly scoped. Explain its goal, required inputs, safe procedure, expected output, and failure conditions. A skill is instruction, not a permission grant.

Manual skill paths that no longer exist are shown as warnings. Remove or repair them before relying on that profile.

Approval policies

Choose whether tools run automatically, ask according to risk, always ask, or use an approved list. Use always-ask for sensitive publication, account changes, external sends, and other actions where each set of arguments matters.

Test the profile

Start with a harmless read-only request. Confirm the correct background profile starts, the expected tools are visible, disallowed tools remain absent, and approval prompts identify the background agent clearly.

For tools not supplied by an integration, continue to custom tools.