> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/investing/risk-adjusted-performance/tail-ratio/usage.md).

# Usage

Tail Ratio Usage

The Tail Ratio is best used to understand the underlying risk and reward profile of an asset before entering a position or to manage risk on active trades.

### How it works

The indicator calculates the return of each bar over the defined lookback period. It then finds the specified upper percentile (e.g., 90th) and lower percentile (e.g., 10th) of these returns. The Tail Ratio is simply the absolute value of the upper percentile divided by the absolute value of the lower percentile. The resulting value is then optionally smoothed using an EMA to create the final oscillator.

### Interpreting the Ratio

* **Right-tailed / Positive Skew (Above Upper Guide, e.g., > 1.20)**: The right tail is "fatter" than the left. This indicates that extreme upside moves are larger than extreme downside moves. The market has a bullish structural bias and is prone to upside volatility.
* **Symmetric / Normal (Around 1.0)**: The tails are roughly equal. Extreme gains and extreme losses are balanced in magnitude. The market is not showing a strong directional bias in its volatility.
* **Left-tailed / Negative Skew (Below Lower Guide, e.g., < 0.80)**: The left tail is "fatter" than the right. Extreme downside moves are larger than extreme upside moves. The market has a bearish structural bias and is highly susceptible to downside shocks.


---

# 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.candelacharts.com/investing/risk-adjusted-performance/tail-ratio/usage.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.