What is Agent Skill Library?
Also called skill library, capability library.
An agent skill library is a collection of packaged procedures an agent can load when a task calls for one, each describing how to carry out a specific job step by step. Skills are kept separate from the agent's standing instructions so that only the relevant ones occupy its working context. A library can be shared across several agents and across teams.
The design addresses a practical limit. Everything an agent reads for a task competes for a bounded context window, so pushing every procedure into the standing instructions makes the agent slower, more expensive to run, and less focused on the task in front of it. A library keeps a short index in view and loads the full procedure only when it matches what is being asked.
Organizations use libraries to capture the parts of a job that are stable and repeatable: how to format a quote, how to check a refund against policy, how to escalate an outage, how to structure a research brief. The same skill can then be attached to several agents, which is how consistency is maintained without copying identical instructions into many places.
Skill is used inconsistently across products. In some it means a written procedure, in others a tool or API connection, and in others a purchasable add-on. When evaluating, check whether skills are versioned, whether an agent can be prevented from using one, and whether the agent decides for itself when to load a skill or must be told explicitly.
A skill is narrower than an agent template, which configures an entire role, and it is usually written from an existing standard operating procedure. Where a marketplace exists, skills are commonly distributed through it. Tools and skills differ: a tool is the ability to act on a system, while a skill is knowing how and when to do so.
Key points
- Packaged procedures loaded only when they are relevant
- Keeps standing instructions short and the agent focused
- One skill can be shared across many agents
- The word means different things across products
In practice
A managed services company writes a skill called incident escalation. It lists the severity levels, who is notified at each level, the wording of the customer update, and the point at which a person must take over. Three different agents share it, so a database alert and a website outage produce the same shape of update, in the same order, to the same people.