> For the complete documentation index, see [llms.txt](https://brightid.gitbook.io/aura/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brightid.gitbook.io/aura/how-to-play/level-up.md).
# Level Up
The "Level Up" tab of your home screen will tell you what to do to reach the next Aura Player level.
As [Aura Trainers](/aura/roles/trainers.md) submit positive evaluations of you, your Aura Player score and level will increase. The higher your Player level, the greater your ability will be to help people get verified.
You unlock the ability to be evaluated by Trainers once you've made your third evaluation.
## Finding Trainers
Find Trainers section of the Level Up tab
The Level Up tab will show which of your BrightID connections are Trainers. It will also show which of your connections are Players, so that you can find Trainers through them.
You should contact Trainers and ask them to review your evaluations.
{% content-ref url="/pages/nsPMVX4UlMGFmdLfYraw" %}
[Trainers](/aura/roles/trainers.md)
{% endcontent-ref %}
## Viewing your Evaluations
Once you've received an evaluation from a Trainer, you'll see it in the "Level Up" tab. If an evaluation is low, you can ask the Trainer that gave it to you what you can do to improve it.
Trainer evaluations in the Level Up tab
---
# 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://brightid.gitbook.io/aura/how-to-play/level-up.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.