Custom agents, skills, and tools

Create reusable agent configurations, add skill files, and choose the tools each custom agent receives.

Create a custom agent

A custom agent is a preset: instructions, skills, MCP servers, and tool policy. Give it a role that you will use repeatedly, such as an accessibility reviewer or a maintainer familiar with your project conventions.

1. Open Settings → Custom Agents and confirm the selected host.
2. Create a definition with a recognizable name and a short description.
3. Write instructions describing its responsibility, expected output, and boundaries.
4. Select the skills and MCP servers it should receive, and review its tool policy.
5. Save the definition and choose it when launching a new conversation.

You review user-facing changes for accessibility. Explain the impact on keyboard and screen-reader users. Cite the relevant file and location for every finding. Propose concrete corrections and do not edit files unless asked.

Add a skill on the host

Skills are discovered from the filesystem. On the host where your agents run, create a folder under ~/.tyde/skills/ and put its instructions in SKILL.md. Open Settings → Skills and choose Refresh to re-scan.

~/.tyde/skills/
└── project-review/
    └── SKILL.md

A small skill can capture a review procedure:

---
name: project-review
description: Review this project's user-facing changes
---

Read the project instructions before reviewing.
Explain each finding with its user impact and file location.
Check loading, empty, error, and keyboard-interaction states.
Return findings in priority order, with a proposed correction.

Refresh the list, then assign the skill to the custom agents that need it. The default agent uses all host skills; a custom definition lets you choose its skill set.

How backends receive shared configuration

Tyde makes host skills and agent definitions available through its backend integrations. This lets you maintain common instructions while choosing different harnesses for different tasks.

Shared configuration does not mean every harness has identical tools, model options, permissions, or skill behavior. Check the session’s backend and capabilities, and keep instructions clear about the desired outcome.

Host scope and MCP servers

Custom agent changes are saved on the selected host. Adding a skill to your laptop does not add it to a remote host. If you want the same specialist on two servers, maintain the definitions and skill files on both.

MCP servers add tools or resources to the agent. Configure them under Settings → MCP Servers, then choose which ones a custom agent should receive. Configure executable paths and credentials for the host that runs them.