Tools and Skills
Control runtime tools and attach reusable instructions to an Assistant.
Open an Assistant and select Tools & Skills. This section controls runtime capabilities and reusable instructions.
Built-in tools
| Tool | Default | Current behavior |
|---|---|---|
| Search knowledge | On | Searches connected Knowledge and returns cited answers. |
| Session memory | On | Uses information from the current conversation session. |
| Fetch URL | Off | Reads a URL when the runtime selects the tool. |
| Show a table | Off | Shows facts in a table when the runtime selects the tool. |
Search knowledge is always available. You can enable or disable the other built-in tools.
Show a table arranges facts that the Assistant found in this answer. It does not calculate values. The table appears above the written answer, and the Inbox transcript shows the same table.
The Assistant can add a follow-up question to a row. The Visitor selects the row to ask that question. The Inbox transcript shows these rows, but a Member cannot select them.
Enable Study Mode
Study Mode is off by default. Enable it to let Visitors practise the Assistant's Knowledge with interactive exercises.
- Open Tools & Skills and enable Study Mode.
- Enable at least one question format.
- Add Custom instructions to set the teaching style.
- Test an exercise in Preview.
- Publish the Assistant to update the Widget.
The chat composer shows a Study exercises button. Select a format, add a topic, then send the request.
When enabled, Study Mode also appears in Flows. Its settings button opens this section. Disable Study Mode in Tools & Skills. The Flow has no separate switch. Requests from the Study exercises menu go directly to this Flow. A graduation-cap icon appears in Thinking.
Exercises need relevant material in the Assistant's Knowledge. If no material is found, the Assistant asks for a supported topic or study material.
| Format | How the Visitor answers |
|---|---|
| Multiple choice | Select one option. No free-text answer is available. |
| Drag the words | Drag or select a word to complete one blank per question. |
| True / False | Select one of two options. |
| Flashcards | Type the missing word or a short phrase. |
Choose for me selects an enabled format. Each exercise contains at most five distinct questions based on retrieved Knowledge.
Select Check to save an answer. Ciele shows whether it is correct, the correct answer, and an explanation. A submitted answer cannot be changed. Flashcards accept the spelling variants defined when the exercise was created.
The Inbox shows the questions, submitted answers, correct answers, and score. Unfinished exercises show how many questions remain unanswered. The exercises run inside the chat. They do not need an external H5P player.
Connect structured data
The Data section lists Entities imported through Settings → Data. Select each Entity that this Assistant may query.
Each selected Entity provides an exact filter tool. An Entity with text attributes also provides a keyword search tool.
Shared Entities are available to every Visitor served by the Assistant. User-scoped Entities require a verified identity claim.
The Entity selection and schema enter the next Publication snapshot. Record content remains live after Publication.
See Entities and Records for CSV imports, scope choices, and identity filtering.
Configure one API integration
An Assistant can use one registered API integration. The integration contains a base URL, a protected credential, and described endpoints.
For each endpoint, define the method, path, purpose, parameters, and response shape. The runtime validates every requested path against this catalogue.
The agent can inspect endpoint details before it sends a request. Large responses remain available through windowed reads.
Control the endpoint catalogue
Add only the endpoints that the Assistant must use. The runtime cannot call an unregistered path through this integration.
Prevent a duplicate write
A request can be sent again after a timeout or a failure. If the endpoint writes data, the second request can make a second record.
To prevent this, give the endpoint an idempotency key. In the endpoint form, type where your API reads the key:
header:Idempotency-Keysends the key in a request header.body:request_idsends the key in the JSON body.
Use the name that your API reads. Ciele does not guess this name. Different APIs read different names.
Ciele makes one key for each call. A retry of the same call sends the same key. A different call sends a different key. Your API can then see the two requests as one write.
Your API must also do its part. It must store the key and return the first result when it sees the key again.
An endpoint with no key is not protected
If you give no key, a retry of the call can write two times. A GET endpoint does not need a key, because a read does not change data.
Attach an Organization Skill
A Skill is a reusable instruction template. An Organization can attach the same Skill to multiple Assistants.
- Open Tools & Skills.
- Find the required Organization Skill.
- Attach the Skill to the Assistant.
- Test the result in Preview.
- Publish the Assistant when the result is correct.
Skill changes are available in Preview immediately. The published Widget uses the last Publication snapshot.
Let people start a Skill from the chat window
A Skill can have an Opening line. Write it as the person who asks, not as the Assistant.
The chat window shows a / menu with each Skill that has an opening line. When the user selects a Skill, the chat window writes the opening line into the message box. The user can edit the text before they send it.
If the opening line is empty, the Skill does not show in the / menu. The Skill prompt continues to apply to each answer.
Publish the Assistant after you write an opening line. The Widget uses the last Publication snapshot.
Attachments and Knowledge are not the same
An attachment and a Knowledge Source both become text, and Ciele reads both with the same extractor. What happens next is different.
A Knowledge Source is permanent. Ciele enriches it, indexes it, and the Assistant can cite it in every later conversation.
An attachment belongs to its conversation. Ciele reads it one time, discards the bytes, and never adds it to the Library. No other conversation sees it.
To make a file permanent, add it in Library instead.
Test the configuration
Ask one question that requires each enabled tool. Inspect the Thinking panel and Sources before you publish.
For structured data, test an exact attribute lookup and a text search. Test user-scoped access with two different signed-in accounts.