> 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/faqs.md).
# FAQs
Tail Ratio FAQs
What is a "good" Tail Ratio to look for?
A Tail Ratio above 1.0 (and especially above the Upper Guide, like 1.20) generally indicates a favorable risk profile where upside potential outweighs downside risk. However, it should be used in conjunction with other indicators rather than as a standalone buy/sell signal.
Should I use Log Returns or Simple Returns?
Log returns are generally preferred for financial time series analysis because they are time-additive and symmetric. However, for shorter timeframes, simple returns are often sufficient. We recommend experimenting with both to see which fits your specific asset and timeframe best.
Why is the Tail Ratio sometimes blank or very erratic?
If the asset has extremely low volatility (e.g., stablecoins or low-volume periods), the lower percentile can approach zero. The indicator has built-in protections against division by zero, which may cause it to temporarily flatline or clamp values to prevent massive, unreadable spikes.
Can I use this for short-term day trading?
Yes. While it is highly effective on higher timeframes (Daily, Weekly) for structural analysis, you can lower the Lookback Length (e.g., from 60 to 20) to make the oscillator more responsive for lower timeframe day trading.
How do I interpret the colored oscillator line?
The line changes color based on the neutral 1.0 level. It is colored Teal when the Tail Ratio is above 1.0 (Positive Skew), indicating favorable upside conditions, and Orange when it is below 1.0 (Negative Skew), highlighting increased downside risk.
---
# 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/faqs.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.