> For the complete documentation index, see [llms.txt](https://docs.myjuicebox.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myjuicebox.io/building-reports/story-designer/slices/charts/leaderboard.md).

# Leaderboard

The leaderboard chart displays which dimensions rank at the top (or bottom) across multiple measures. Adding a slice with a leaderboard chart (i.e., a leaderboard slice) is a good choice when users want to quickly see the "winners" and "losers."

## Adding a leaderboard slice

To add a leaderboard slice:

* select **Leaderboard** from the chart list

![Select Leaderboard from dropdown](https://872636700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmfYn9Ab4YpIl0ZZFm-%2Fuploads%2FC3UGIXCE8q8FMsdYoibz%2Fimage.png?alt=media\&token=356ea112-7a38-41f6-87aa-36ccbad14266)

* select the column with the values you want to be ranked
* select the measures by which you want to rank the column values
* select the max rows
* add slice text (optional)

![A leaderboard slice](https://872636700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmfYn9Ab4YpIl0ZZFm-%2Fuploads%2FcqsurRsITxFIDZc0D5M4%2Fimage.png?alt=media\&token=9b91a36f-af73-4e6f-af22-24b4c192773a)

{% embed url="<https://www.loom.com/share/78c8a8a487044fffafeed1e34d3c87bd>" %}
Adding a leaderboard slice
{% endembed %}

## Using a leaderboard slice

If you have 10 rows in your leaderboard, you can use the **LOOK AT** options to see the top 10, bottom 10, or top 5 and bottom 5. (If you have 25 rows, you can opt to see the top 25, bottom 25, or top 13 and bottom 12). To see the ranking of a column value not shown in the leaderboard, you can click the filter pill and search for the dimension. Selections made in the leaderboard slice will filter downstream slices.


---

# 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.myjuicebox.io/building-reports/story-designer/slices/charts/leaderboard.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.