> For the complete documentation index, see [llms.txt](https://help.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stockcharts.com/charts-and-tools/reports-and-galleries/predefined-technical-alerts.md).
# Predefined Technical Alerts
The [Predefined Technical Alerts](https://stockcharts.com/freecharts/alertsummary.html) page shows when common indexes, sectors, commodities, and breadth indicators cross above or below various levels.
You can access the Predefined Alerts page from the **Reports & More** area of the [Charts & Tools](https://stockcharts.com/freecharts/) page or the Y**our Alerts** area of [Your Dashboard](https://stockcharts.com/def/servlet/Favorites.CServlet).
## Report Format
Two major sections in the Predefined Technical Alerts report are **Today's Alerts** and **Past Alerts**. Alerts triggered on the current trading day will appear in the **Today's Alerts area**, while past alerts are displayed in **Past Alerts area**.
Alerts are updated every few minutes during the trading day. Bullish events have a green background, while bearish events have a red background.
The alert description and the time it was triggered (Eastern time) are displayed. If you click on the alert name you'll see a chart of the underlying symbol.
## Additional Resources
### Videos
{% embed url="" %}
---
# 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://help.stockcharts.com/charts-and-tools/reports-and-galleries/predefined-technical-alerts.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.
