> For the complete documentation index, see [llms.txt](https://simpleaitrading.gitbook.io/simple-ai-trading/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://simpleaitrading.gitbook.io/simple-ai-trading/toolkit-screener/how-to-use.md).

# How to Use

## About the Signals

The signals provided by our screeners are exactly the same as the ones you would receive if you loaded the indicator directly on your TradingView chart using the same settings.

The primary purpose of the screeners is to give you early alerts on potential market moves across the timeframes you have selected — allowing traders to react quickly and execute trades in real-time based on their chosen strategy.

## Why Use Screeners?

Monitoring multiple charts all day can be time-consuming and mentally exhausting. Most traders simply don’t have the time or resources to constantly watch every market and timeframe.

That’s exactly where our screeners come in.

The screeners do the heavy lifting for you — scanning the markets 24/7 and sending you instant alerts the moment a signal is generated. This allows you to stay focused and act quickly when trading opportunities appear, without needing to stare at charts all day.

## Important to Understand Before Using Signals

Each screener is built around its own unique trading toolkit — and every toolkit is designed based on a specific core principle of how markets behave.

Some toolkits are built around *Volume*, others around *Momentum*, while some might focus on *Trend Behavior*, *Volatility*, or *Order Flow*.

Because of this, it's very important to understand the strategy behind each toolkit before acting on the signals it provides.

Signals are not meant to be followed blindly — they work best when used in combination with the strategy and logic the toolkit is built on.

## Don'ts — What to Avoid

### Example 1 — Volume Snipe Signals

→ You receive a *Volume Snipe* Buy signal → you check the chart → you place a trade immediately.

> *Mistake:*\
> You didn’t check the current volume activity.

> *Best Practice:*\
> If you're using the *Volume Snipe* strategy, make sure there is sufficient volume activity at the time the signal is generated. The entire strategy relies on strong buying or selling pressure to be effective.

No volume = Lower probability of success.\
High volume = Strong confirmation of the signal.

### Example 2 — Momentum-Based Signals

→ You receive a momentum-based Buy signal (from a toolkit like *Impulse Trend* or *Sniper Trend*) → you place a trade instantly.

> *Mistake:*\
> You didn’t check the current market conditions — like volatility or liquidity.

> *Best Practice:*\
> Momentum signals require active market conditions — with strong price swings, volatility, and liquidity.

If the market has been slow, flat, or lacking liquidity, momentum signals lose their edge and may not perform well.

## Golden Rule

→ Always combine the signal with *context*.

→ Ask yourself:

* *Is volume supporting the signal?*
* *Is momentum present?*
* *Is volatility sufficient?*
* *Is liquidity good?*

When you align these conditions with the signals generated by our toolkits — that's when you'll dramatically improve your probability of success.


---

# 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://simpleaitrading.gitbook.io/simple-ai-trading/toolkit-screener/how-to-use.md?ask=<question>&goal=<endgoal>
```

`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.