> For the complete documentation index, see [llms.txt](https://wiki.mypet-plugin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.mypet-plugin.com/setup-guide/skilltree-creation/creating-custom-skilltrees/requirements.md).
# Requirements
Skilltree requirements are used to limit skilltrees to pets that meet certain conditions.
The `Requirements` section of the [Configurator's](/setup-guide/skilltree-creation/creating-custom-skilltrees.md) Inspector allows you to configure optional requirements that must be met in order to be able to use the skilltree.
### Requirements List
#### `NoSkilltree`
* Limits this skilltree to pets that have no skilltree yet.
#### `Skilltree`
* Limits this skilltree to pets that have a certain skilltree.
* Requires the skilltree name as a parameter.
* Example:
* `Skilltree:Ride`
#### `Permission`
* Limits this skilltree to pets where the owner needs the `MyPet.skilltree.` permission.
* The permission node can be changed by providing a parameter.
* Example:
* `Permission:newNode` will become `MyPet.skilltree.newNode`.
#### `PetLevel`
* Limits this skilltree to pets that have a certain level.
* Can be limited to:
* a specific level
* a minimum level
* a maximum level
* Examples:
```
PetLevel:min=2
PetLevel:min=2:max=4
PetLevel:max=2
PetLevel: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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.mypet-plugin.com/setup-guide/skilltree-creation/creating-custom-skilltrees/requirements.md?ask=&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.
