> For the complete documentation index, see [llms.txt](https://docs.owkin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.owkin.com/what-you-can-do-with-k-pro/target-identification-and-indication-discovery/explore-a-cohort.md).
# Explore a cohort
**What to do:** Start by asking K-Pro about a cohort's composition to understand what's available before diving into specifics. Always specify the exact TCGA cohort code (e.g., TCGA-BRCA, TCGA-LUAD) rather than the disease name alone.
**Which tool:** Plotter (clinical characterization)
**Example prompt:**
> Provide clinical characteristics of the TCGA-BRCA cohort. Include the distribution of tumor stage and age at diagnosis.
**Expected result:** A clinical characteristics table (often called a "Table 1") and/or distribution plots showing the clinical breakdown of the TCGA-BRCA cohort. Continuous variables are summarized as mean (SD) or median \[IQR], categorical variables as counts and percentages, with a column for missing data.
**Follow-up:**
> Show the same clinical characteristics stratified by tumor stage, and test for differences between stages.
When you stratify by a group, the table adds between-group p-values so you can spot imbalances before a comparison.
[**A-S-R-T-C breakdown**](https://docs.owkin.com/getting-started/prompting-guide-and-prompt-library)**:** Show \[A] clinical characteristics \[S: cohort variables] at bulk level \[R] as summary tables \[T] in TCGA-BRCA \[C].
---
# 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.owkin.com/what-you-can-do-with-k-pro/target-identification-and-indication-discovery/explore-a-cohort.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.
