> For the complete documentation index, see [llms.txt](https://docs.ag5.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ag5.com/skills/level-descriptions.md).
# Level descriptions
### 1. What is a level description?
A textual description of what each level means.\
(levels that are set as achieved result or minimum requirement)
### 2. What is the purpose of a level description?
To make sure every user has the same understanding of what exactly each level means.\
In the picture below, you can see the level descriptions that are specifically defined for the skill "Drilling".
This is especially important when different users can create new skill results (e.g. when you have many trainers or are using self-assessments). They need to have the same understanding of what each level means.
### 3. How to create level descriptions?
You can define general level descriptions within a rating scale, or specifically within a skill. And these level descriptions can be made visible while adding skill results.
Read in [this article](/skills/rating-scales.md) how you can define general level descriptions within a rating scale.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ag5.com/skills/level-descriptions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.