> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/class-management/report-cards/report-cards-setup.md).
# Creating questions for each ability level
### Ability Level Significance
Report cards are structured using ability levels in flaik. Report Card questions should be created to correspond with your resort's Ability Levels. After all, a beginner will benefit from different questions on their report card than someone at a higher level working on more advanced techniques.
### Creating Questions
Report Card questions are set for each Ability Level within each Discipline.
* Under the Default drop-down, you will find all of the Ability Levels your resort has configured within Disciplines and Ability Levels.
* If you wish, you can also specify different Report Card questions only for certain tasks. This is useful if you have a set of teaching tasks, such as programs, that might need some special criteria.
Questions must be entered for each Ability Level your resort offers lessons in.
* Each question should be brief, describe a skill, and each question should be answerable by selecting **Working on it**, **Can do sometimes**, and **Got it**.
* Non-applicable questions can be left without a selection and will not appear in the Report Card email.
{% hint style="info" %}
Ability Levels used in these demo images may be different than the levels used at your resort.
{% endhint %}
### Ordering Questions
Any questions that are no longer needed can be deleted using the trash can icon (3).
---
# 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://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/class-management/report-cards/report-cards-setup.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.
