> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/advanced/custom-lessons.md).

# Custom lessons

Create your own lessons with Studio, such as internal procedures or IT policies, and add them to the training path alongside Stoïk's lessons.

1. Go to `Learning` > `Studio` and click `Create thematic`.
2. Add your content and quiz questions. The lesson stays in **Draft** until every required field is filled, then becomes **Ready**.
3. Go to `Learning` > `Training` > `Library` and add the lesson to the training path. Only **Ready** lessons can be added.

{% hint style="info" %}
Once a lesson is in the training path, you can still correct its text, but you can no longer add or remove lessons or quiz questions. This protects employees who are already working through it. To make bigger changes, remove the lesson from the training path first.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/human-security/advanced/custom-lessons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.