This page is machine-translated from French. Read the French original.

Skills library

The library contains instruction sheets — instructions written in natural language, which an agent loads when needed.

To be distinguished from SKILLS, which are tools that execute code. A library card does nothing by itself: it explains how to do.


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 constantly aware of the title and description of each active record — a few lines; ;
  • When a record matches the request, he loads it full 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 — it is she who determines when the agent charges her, so she must be precise; ;
  • THE body : steps, rules, expected formats, examples, pitfalls to avoid; ;
  • of the resources Optional: templates, reference examples.

Two sources

The catalogue provided. A set of fact sheets included with the application, covering general needs: office document production, analysis and research, content creation, file organization, and materials preparation. This catalog is read-only.

Your own index cards. An administrator adds as many as needed for your internal procedures. A record with the same name as the one provided replaces it.


Activate and manage — administrator

Réglages → Agents, skills library section.

  • The available catalogue is displayed there; ;
  • Each card can be activated or deactivated individually; ;
  • only active records are announced to the agents.

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. The agent decides to load the file on her alone.

  • Low: "Help with documents."«
  • Good: "Write a meeting report using the internal model: participants, decisions, actions with responsible party and deadline. Use this whenever a transcript or meeting notes need to be formatted."«

The body is written like an instruction to a new collaborator. Numbered steps, explicit decisions, precise output format, complete example, and a list of classic 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

  • She does nothing. A guide explaining how to query a database assumes that SQL skills are enabled.
  • She does not guarantee that the agent will follow the procedure to the letter. She makes that much more likely, not certain.
  • She does not replace the system prompt, which remains the right place for what applies to all messages in a space.