Tools & Skills

Tools and skills are how agents act. Tools give an agent the ability to take actions — search the web, generate files, call external services. Skills package higher-level capabilities the agent can recall when relevant.

Tools

Tools are grouped into categories. When you build an agent you grant it specific tool_categories, and the planner chooses which tool to invoke at each step. Tools can be enabled or disabled per team.

GET /api/tools                                 # list tools
GET /api/teams/{team_id}/tools                 # team tool config
GET /api/teams/{team_id}/tools/available
PUT /api/teams/{team_id}/tools/{tool_name}/enabled

Skills

Skills are reusable, packaged capabilities. Xagent ships with a library of built-in skills:

Skill	What it does
agent-builder	Helps design and configure new agents.
evidence-based-rag	Retrieval with citations back to source documents.
presentation-generator	Builds slide presentations.
pptx-editorial / html-deck-editorial	Editorial-quality decks in PPTX or HTML.
pdf-report-editorial	Long-form, formatted PDF reports.
xlsx-financial-report	Structured financial spreadsheets.
poster-design	Marketing posters and visual assets.

GET  /api/skills                 # list skills
GET  /api/skills/{skill_name}    # skill detail
POST /api/skills/recall          # recall a skill for a task
POST /api/skills/reload

Built-in Connectors

Connectors link an agent to an outside service you already use. Sign in once and the agent can act in that service on your behalf — no configuration files, no code.

Category	Connectors
Productivity	Notion, Google Sheets, Google Docs, Google Slides, Google Drive, Google Calendar, Google Maps, Granola, OneDrive
Communication	Gmail, Outlook, Slack, Microsoft Teams
Marketing	Google Analytics, Google Ads, LinkedIn, Facebook, Instagram
CRM	HubSpot
Scheduling	Zoom
Operations	AWS

See MCP Providers for the sign-in steps on the connectors that need their own app credentials.

Sharing a connector lets your teammates' agents use that integration, so not everyone has to connect the same account separately.

Action	Who can do it
Share a connector with the team	The person who owns the connection
Stop sharing it	Team admins only

A shared connector cannot be un-shared while a team agent still uses it — remove it from that agent first.

When a shared connector needs your sign-in

Some services still require each person to sign in with their own account. When a teammate shares one of those, it appears in your list marked as needing setup — the connector is available to you, but you have to authorise it with your own credentials before an agent can use it.

Extending the Toolset

Beyond the built-ins you can connect external capabilities:

MCP Servers → — connect Model Context Protocol servers
Custom APIs → — register your own HTTP APIs as tools