> 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/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies.md).

# Scanning Case Studies

Each of these in-depth case studies walks you through writing a specific type of scan, discussing the most effective scanning techniques, showing the preferred syntax in example scans, and pointing out any potential pitfalls.

### Scans for Conditions and Signals <a href="#getting_started" id="getting_started"></a>

* [**Scanning for Crossovers**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-crossovers.md)
* [**Scanning for "Near Crosses"**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-near-crosses.md)
* [**Scanning for Divergences**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-divergences.md)
* [**Scanning for Relative Strength**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-relative-strength.md)
* [**Scanning for Consolidation and Breakouts**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-consolidation-and-breakouts.md)
* [**Scanning for Selling Climaxes**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-selling-climaxes.md)

### Scans for Patterns and Indicators

* [**Scanning for SCTRs**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-sctrs.md)
* [**Scanning Ichimoku Clouds**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-ichimoku-clouds.md)
* [**Scanning for P\&F Chart Patterns**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-p-and-f-chart-patterns.md)

### Defining Your Scan Universe

* [**Scanning Your ChartLists**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-your-chartlists.md)

### Scans Using Functions and Operators

* [**Scanning for an Overlay of an Indicator**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-for-an-overlay-of-an-indicator.md)
* [**Writing Min/Max Scans**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/writing-min-max-scans.md)
* [**Writing Percentage Change Scans**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/writing-percent-change-scans.md)
* [**Scanning Over a Range of Dates**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/scanning-over-a-range-of-dates.md)
* [**Writing Scans with OR Clauses**](/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies/writing-scans-with-or-clauses.md)


---

# 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/scanning-and-alerts/scan-writing-resource-center/scanning-case-studies.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.