> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-administrators/toolbox.md).

# AI Toolbox

The administrator's side of the AI Toolbox: building the elements your colleagues run.

## What the Toolbox is

An assistant is a conversation. The Toolbox is a form.

Where an assistant needs the user to know what to ask, a Toolbox **element** puts a short form in front of them (a few fields to fill in) and returns a finished result. The prompt engineering happens once, when you build the element. Everyone who uses it gets the benefit without having to know anything about prompting.

This is usually the fastest route to adoption in an organisation. People who would never think of a good prompt will happily fill in three fields.

## The pieces

| Piece               | What it is                                                     | Page                                                               |
| ------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------ |
| **Element**         | One tool: a template, a set of input fields, and a model.      | [Elements](/en/for-administrators/toolbox/elements.md)             |
| **Category**        | Groups elements in the sidebar so a long list stays navigable. | [Categories](/en/for-administrators/toolbox/categories.md)         |
| **Default values**  | Shared pick-lists that fill dropdowns inside elements.         | [Default values](/en/for-administrators/toolbox/default-values.md) |
| **Library**         | Sharing elements between organisations.                        | [Library](/en/for-administrators/toolbox/library.md)               |
| **Quality control** | Automated checks that an element keeps producing good output.  | [Quality control](/en/for-administrators/quality.md)               |

## What makes a good element

Look for work that is **repetitive, structured and currently done inconsistently**:

* Writing a standard kind of message: a rejection letter, an appointment confirmation.
* Summarising a recurring document type into a fixed shape.
* Rewriting text into your house style.
* Translating while keeping terminology consistent.
* Extracting fields from a document into a table.

Poor candidates are open-ended tasks with no repeatable shape. Those belong in an assistant conversation, where the user can steer.

## How to build one

1. **Find a real example.** Take a task someone does regularly and get two or three real inputs and the outputs they would consider good.
2. **Decide the inputs.** What genuinely varies between runs? That is your form. Keep it short. Every field is friction.
3. **Write the template.** The instruction, with the inputs slotted in.
4. **Test with the real examples.** Compare against the outputs you collected.
5. **Publish it**, put it in a category, and tell people it exists.

The most common mistake is asking for too much on the form. Five fields where two would do turns a thirty-second job into something people avoid.