> For the complete documentation index, see [llms.txt](https://docs.kostacloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kostacloud.com/quick-start-guide/2.2-first-analysis-dashboard.md).
# 2.2 First Analysis Dashboard
How to create an Analysis Dashboard and look at the spot diagram
Here we describe a step-by-step process from taking the Optimized Singlet designed in the previous tutorial to show a Spot Diagram.
First we ask that you navigate to the [CLOUD Dashboard](https://cloud.tsaspc.com) and open the Project from the previous tutorial, which should look similar to the below:
Singlet from Previous Tutorial
Switch Navigation Tabs to Analysis Mode. Your window should look something like this:
Blank Analysis View
Now you can create an Analysis Dashboard by scrolling in the Action Pane to the far right and clicking "". Now it should look like this:
New Dashboard
Now Simply Click and Drag the Spot Diagram icon from "Imaging" Simple Plots to the Dashboard. Now you have a Spot Diagram!
Simple Spot Diagram.
---
# 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.kostacloud.com/quick-start-guide/2.2-first-analysis-dashboard.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.
". Now it should look like this:
