> 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/interactive-data-visualisations/prompting-for-a-plot.md).
# Prompting for a plot
**What to do:** Specify the chart type, variables, and dataset. K Pro supports real-time plot iteration: ask for specific formatting changes (colors, labels, font size) in follow-up prompts rather than trying to specify everything at once.
**Which agent/skill:** Visualization Agent
**Example prompt:**
> Create a Kaplan-Meier survival curve for TCGA-BRCA patients stratified by TP53 mutation status (mutated vs. wild-type). Include the p-value from a log-rank test and the number of patients at risk.
**Expected result:** A Kaplan-Meier plot with two curves, log-rank p-value, and at-risk table.
[**A-S-R-T-C breakdown**](https://docs.owkin.com/getting-started/prompting-guide-and-prompt-library)**:** Create \[A] TP53 mutation survival analysis \[S] at bulk level \[R] as a KM curve with log-rank test \[T] in TCGA-BRCA, mutated vs. wild-type \[C].
#### Create comparative visualizations
**Prompt:**
> Create a box plot comparing the expression of CD274 (PD-L1) across the five molecular subtypes in TCGA-BRCA. Add individual data points and mark statistically significant pairwise comparisons.
**Expected result:** A box plot with overlaid data points and significance brackets between groups.
**Follow-up:**
> Now create a heatmap of the top 50 differentially expressed genes between these molecular subtypes.
**Tip:** You can request multiple plot types in sequence. Each builds on the data context from the previous query.
---
# 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/interactive-data-visualisations/prompting-for-a-plot.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.
