In Insulin, an integration is a connected system an agent is allowed to reach, a tool is an action the agent takes against that system, and a skill is a reusable capability you add to an agent to extend what it can do — three distinct things the industry too often calls by each other’s names.
Ask three AI platforms what a “skill” is and you’ll get three answers, and at least one of them will mean what another calls a “tool.” The vocabulary is a mess, and it matters, because when you’re configuring an agent you’re making real choices about what it can reach, what it can do, and what it reuses.
Here is the distinction as Insulin draws it, so you can stop translating between vendors’ dictionaries and design the agent you actually need.
Integration: what an agent is allowed to reach
An integration is a connected external system — a CRM, a data warehouse, a ticketing tool — that an agent can be granted access to. In Insulin, integration access is scoped: you allowlist the specific systems an agent may use, and that scope is the boundary. An agent cannot reach data outside the integrations you grant it.
This is the most important of the three to get right, because it’s the security boundary. A support agent scoped to your help desk and knowledge base simply cannot touch the billing system, no matter what it’s asked. Scope is covered in depth in scoping an agent to its integrations — the short version is that an integration is a door you open deliberately, one system at a time.
Tool: the action taken against an integration
A tool is an action an agent executes against an integration it has access to — reading a record, creating one, running a query. Tools are how an agent does something rather than just answering. In Insulin, tool execution runs through approval: the agent proposes a plan, and you approve or reject it before any tool runs.
The relationship to notice: tools run against integrations. An agent granted the CRM integration can use CRM tools; revoke the integration and the tools go with it. You don’t grant tools directly — you grant the integration, and the tools it exposes come with it, gated by the approval step so nothing acts without a person’s say-so.
Skill: the reusable capability you add
A skill is a reusable capability you add to an agent to extend what it can do. Unlike an integration (a connection) or a tool (an action), a skill is a package — a way of working that you attach to an agent, including skills installed from the Insulin Marketplace. One agent’s useful pattern becomes a skill others can load.
The distinction from an agent itself is the one people miss: an agent is a whole specialist (its instructions, model, integrations, and skills together); a skill is one capability you bolt onto an agent to extend it, not a replacement for it. We draw that line in agents and skills. If you find yourself rebuilding the same capability across several agents, that capability wants to be a skill.
How they fit together
The three compose into an agent:
- Integrations define the agent’s reach — the systems it’s allowed to touch.
- Tools are what it does with that reach — the actions, each gated by approval.
- Skills are the reusable capabilities you add on top, from your own library or the Marketplace.
So when you’re configuring an agent and wondering which lever to pull: if you want the agent to reach a new system, add an integration. If you want it to do something new in a system it already reaches, that’s a tool it already has. If you want to give it a reusable way of working you can share with other agents, that’s a skill.
Frequently asked questions
What is the difference between a tool and a skill in an AI agent? A tool is an action an agent takes against a connected system (read a record, run a query). A skill is a reusable capability you add to an agent to extend how it works. Tools act on integrations; skills are packages you attach and can share across agents.
What is an integration versus a tool? An integration is a connected system an agent is allowed to reach; a tool is an action taken against it. You grant the integration, and its tools come with it — scoped to that agent and gated by approval before anything runs.
Do I grant tools to an agent directly? No. In Insulin you allowlist integrations, and the tools each integration exposes become available to the agent, run through the approval step. The integration is the boundary you control; revoking it removes the tools with it.
When should something be a skill? When it’s a reusable way of working you want on more than one agent. If you keep rebuilding the same capability, package it as a skill — including installing one from the Insulin Marketplace — instead of duplicating it per agent.
Why does the terminology matter? Because each maps to a real configuration choice: integrations set what an agent can reach (the security boundary), tools set what it can do there, and skills set what it reuses. Confusing them leads to over-granting access or rebuilding the same capability repeatedly.
Takeaways
- Integration = a connected system an agent may reach (the security boundary, scoped and allowlisted).
- Tool = an action taken against an integration, gated by approval before it runs. You grant the integration, not the tool.
- Skill = a reusable capability you add to an agent to extend it, including from the Insulin Marketplace — package it when you’d otherwise rebuild it.
- The three compose an agent: reach (integrations), actions (tools), and reusable capability (skills).
Design agents with clear reach, gated actions, and reusable skills in Insulin. Explore agents and the agent marketplace, or book a demo.
Stay Updated
Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.