Assign Tools via Skills
Skills are reusable packages that bundle tools, credentials, and knowledge into a single unit you can assign to agents. This guide shows you how to browse, install, and assign skills.
Prerequisites
- An existing team with at least one agent (see Build a Team)
- Tools or MCP servers configured in your organization (see Connect an MCP Server)
Steps
1. Navigate to Skills
Go to Settings > Skills in the sidebar. This shows all skills available in your organization.
2. Browse available skills
Skills are displayed as cards. Each card shows:
- Name -- The skill's display name
- Tool count -- How many tools are included
- Icon -- A visual identifier
If a skill catalog is available, you also see templates you can install with one click.
3. Create a custom skill (optional)
If no existing skill matches your needs, click New Skill to create one. See Create a Skill for the full process.
4. Open the Team Builder
Navigate to your project, open the team, and switch to the Builder tab.
The sidebar palette has a Skill Library section listing all organization skills. Each skill card is draggable.
5. Drag a skill onto an agent
Drag a skill card from the palette and drop it onto the target agent node on the canvas. This creates a skill assignment linking the skill to the agent.
A skill node appears below the agents row, connected to the assigned agent by a dashed line.
A single skill can be assigned to multiple agents. The skill node is shared on the canvas -- multiple dashed lines connect it to each assigned agent.
6. Verify the assignment
Click the agent node to open the drawer. The agent's skill assignments are listed, showing the tools that the skill provides.
7. Remove a skill assignment
To remove a skill from an agent, click the x button on the skill node in the canvas. This removes the assignment for all agents connected to that skill.
Alternatively, manage assignments through the agent's edit form in the card-based tab.
8. Check credential requirements
Some skills require specific credentials. If a skill's required credentials are not configured in your organization, the tools may fail at runtime.
Navigate to Settings > Credentials to verify that all required credentials are in place.
Skills declare their credential requirements via credential_keys. If a required credential (e.g., GITHUB_TOKEN) does not exist in your organization, the skill's tools will not have access to the necessary API keys at runtime.
What's next
- Configure an Agent to adjust agent settings
- Set Up Assignments to assign agents with skills to workflow stages
- Create a Skill to build custom skill packages