> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/review-tool-concepts/brands-and-attributes/setting-up-attributes/add-variables-to-steps.md).
# Add Variables to Steps
When using linked files (like your Attributes or regulatory databases), Protege AI automatically creates variables you can insert into policy steps for dynamic, context-aware reviews.
These variables can be used in multiple fields within a step, including:
* Explanation
* Prompt
* Keywords
#### To Add a Variable:
1. In the step editor, place your cursor in the field where you’d like to insert the variable (e.g., Explanation).
1. Press the $ key to open the list of available variables.
2. Select the appropriate variable from the dropdown list — this variable pulls matching data from the linked file.
3. Once inserted correctly, the variable name will turn green, indicating it’s properly connected.
---
# 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.tryprotege.com/review/review-tool-concepts/brands-and-attributes/setting-up-attributes/add-variables-to-steps.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.