This page is machine-translated from French. Read the French original.
Skills library
The library contains instruction sheets — procedures written in natural language, which an agent loads when needed.
This is distinct from skills, which are tools that execute code. A library card doesn't do anything by itself: it explains how to do it.
The problem it solves
A generic agent doesn't know your procedures. You can write anything in the system prompt, but it's sent with every message: ten detailed procedures saturate the context, even when none of them are needed.
The library reverses the mechanism:
- the agent is always aware of the title and description of each active record — a few lines;
- When a record matches the request, it loads its complete content.
Result: a lot of know-how available, little context consumed.
How does it look?
A record is a structured document that contains:
- a name;
- a description — this is what determines when the agent charges it, so it must be precise;
- the body: steps, rules, expected formats, examples, pitfalls to avoid;
- Optional resources: templates, reference examples. The agent can only use them if a file system access tool is enabled.
Two sources
The catalogue provided. A set of fact sheets is included with the application. Around thirty cover general needs: producing office documents, analysis and research, content creation, file organization, and media preparation. More than 800 others describe the automation of third-party applications; these bear the MCP badge and only function fully with the MCP server they specify. These originals are never overwritten.
Your own index cards. An administrator can modify a provided record: the modified version replaces the original, which remains restoreable («Restore original»). They can also duplicate it and then adapt the copy to your internal procedures. The screen does not offer the option to create a record from scratch: start with an existing record.
Activate and manage — administrator
Settings → Agent → Agent Skills, Skill Library section.
- The available catalogue is displayed there, with a search and filter by category;
- Each record is activated or deactivated individually; none are active initially;
- Only active records are announced to agents, and activation applies to the entire instance: there is no assignment by space.
Recommendation : Activate only the records that are truly useful. A library with fifteen active records, only three of which are actually used, forces the agent to choose between competing descriptions.
Writing a good fact sheet
The description is the most important part. It is the only part on which the agent decides to load the record, and they only see the first 200 characters.
- Weak : «Help with the documents.»
- Good : «Write a meeting report according to the internal template: participants, decisions, actions with responsible party and deadline. Use this to format a transcript or meeting notes.»
The body of the document reads like a set of instructions for a new colleague. It includes numbered steps, explicit decisions, a precise output format, a complete example, and a list of common mistakes to avoid.
One sheet = one procedure. A sheet that covers three procedures loads for the wrong reason and clutters the context.
Examples of use
| Form | What it contains |
|---|---|
| Meeting minutes | The internal model and writing rules |
| Response to a call for tenders | The expected structure and mandatory information |
| Contract analysis | The checkpoints, in order, and the alert thresholds |
| Customer file | Sections to complete and sources to consult |
| Summary note | The home format, length and level of detail |
What the library does not do
- It doesn't execute anything. A guide explaining how to query a database assumes that the SQL skill is enabled.
- It does not guarantee that the agent will follow the procedure to the letter. It makes it much more likely, not certain.
- It does not replace the system prompt, which remains the correct place for anything that applies to all messages in a space.
