An AI agent alone is just a conversationalist. Skills make it work

An AI agent without skills can explain how to raise a credit note. An agent with skills raises it. Same technology, completely different value to the business, and the difference has nothing to do with the model.

Below: what a skill is, what one costs, and where the boundary sits for what an agent should do without asking.

What a skill actually is

A skill is three things handed to an agent together: access to a specific tool, a procedure for using it, and a boundary on what it must not do.

Access alone is not enough. An agent wired into your invoicing system without a procedure will try, and it will produce a document with a missing field or the wrong tax rate, because it does not know what a correct invoice looks like in your company.

A procedure without access is not enough either. Then the agent describes what should be done, which is the first state exactly: a conversationalist, not an operator.

A skill exists only when all three are present.

Why this is not the same as an integration

An integration is a technical connection. A skill is that connection plus the knowledge of how to use it in your context.

Take a CRM. The integration lets an agent write a contact. The skill knows that a lead arriving with a company number goes down one path, a lead without one goes down another, and a lead from a competitor's domain goes to a human instead.

That distinction has a price consequence. An integration is quoted once. A skill is quoted together with the procedure, and writing the procedure usually reveals that two people in the company do it differently.

What one skill costs

Three bands, depending on what the agent is meant to do.

A read skill, where the agent checks a status, a balance or a date and reports back: usually $700 to $2,000, assuming the system has a sane API.

A write skill, where the agent changes something: $2,000 to $5,000, because permission checks, error handling and the ability to undo all come with it.

A decision skill, where the agent picks a path from rules: $3,000 to $8,000, because the rules have to be written down, edge cases tested, and behaviour designed for the case where the agent is unsure.

Then running costs. Every skill depends on somebody else's system, and other people's systems change. When your CRM vendor revises an API, the skill stops working and somebody has to fix it.

How many skills an agent needs

Fewer than most proposals assume.

A typical customer service agent needs two or three: check a status, log a request, hand the case to a person. The fourth and fifth usually cover situations that arise once a month.

Working rule: add a skill when the process repeats at least a hundred times a month. Below that, build and maintenance do not come back, and every additional skill is another thing that can quietly break.

An agent with three working skills is worth more than an agent with ten, four of which stopped working in March and nobody noticed.

What not to hand an agent

The boundary sits where it sits for any automation.

Decisions about people: hiring, performance review, an individual discount. Regulation requires designed human oversight here, and it is not a box to tick after go-live.

Irreversible actions: deleting data, sending a payment, closing a case with no way back. If a skill would do something you cannot undo, it should end in a proposal rather than an action.

Contested matters. A complaint, a correction, a settlement with an annoyed customer. The agent can log the case and issue a reference number. It should not decide the outcome.

How to work out which skills you need

Take your last hundred requests and group them by what had to be done, not by what they were about.

Usually eighty percent turns out to be three or four actions repeated endlessly: check, log, hand over, confirm. Those are your first skills and they pay back fastest.

The remaining twenty percent, spread across twenty different variants, stays with people. It should.

What happens when you get in touch

We start with your hundred requests and group them for you. The output is a list of three or four skills with a price range against each, not a proposal for an agent.

You talk to the owner, the call runs 45 minutes. If the numbers show no single action clears the payback threshold, we say so and tell you not to build.

If we work together, somebody watches whether the skills still function after the systems they connect to change. That is recurring work, not a one-off, and it is the reason you cannot buy it from a tool.

Your code sits in your repository from day one. The warranty covers repairs at no extra charge.