> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/about-optimizer.md).

# About Optimizer

The Optimizer page displays the available Verified prompts by category and allows you to create Custom prompts based on your requirements. You can run, schedule, and review prompts and their results.

This article walks you through the Optimizer in Avo Assure. It explains the key components of the Optimizer interface and describes the purpose of the available user interface (UI) controls, enabling users to interpret the displayed information effectively.

On the **Optimizer** page (**Home** > Select **Project** > **Design Studio** > **Optimizer**), you can do the following:

1. [**Verified**](/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts.md): Allows you to access the prompts provided by Avo Assure under the following categories:
   * **Authoring Quality**: Includes prompts for reviewing Test Cases, Test Steps, Element Repository elements, Execution Lists, and Data Tables. The prompts cover areas such as repeated test steps, static waits, hardcoded values, test step run times, test case reliability, and naming standards.
   * **Suite Health**: Includes prompts for reviewing Test Cases, Element Repositories, Execution Lists, and Data Tables. The prompts identify items that are empty, unused, inactive for a long time, or do not have an active owner.
   * **Execution Health**: Includes prompts for reviewing test execution results and execution time. The prompts identify repeated test cases in an Execution List, high failure rates, frequent terminations, and increases in Execution List at run time.
2. **Analyze my**: Allows you to send prompts based on specific requirements for your project. 

{% hint style="info" %}
**Note**: The **Custom** section appears only after you send a prompt.
{% endhint %}

3. **Expand All**: Allows you to expand all prompt categories and view the available prompts. 

{% hint style="info" %}
**Note**: Select **Collapse All** to collapse all prompt categories.
{% endhint %}

4. [**Schedule All**](/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/features-in-optimizer/scheduling-a-prompt.md): Allows you to schedule all prompts in the selected category for **Manual Run**, **Daily**, or **Weekly**.

{% hint style="info" %}
**Note**: The **Schedule Selected** option is available only when one or more prompts are selected.
{% endhint %}

5. **Run All**: Allows you to run all prompts in the selected category and automatically updates the **Last Run** date. 

{% hint style="info" %}
**Note**: The **Run Selected** option is available only when one or more prompts are selected.
{% endhint %}

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FBmtDIzqTFier8jiD9BXd%2Funknown.png?alt=media\&token=859cee79-cc4e-4bb2-b24e-90faf0021edf)


---

# 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://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/about-optimizer.md?ask=<question>&goal=<user_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.