> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/overview/quick-guide-to-skyone-studio.md).

# Quick Guide to Skyone Studio

**Skyone Studio** was developed to integrate different applications in a simplified way, without the need for complex programming.

Upon entering, you will find the following features:

{% embed url="<https://app.guideflow.com/player/5pv024xhwr>" %}

* **Studio Home**: Get an overview as soon as you enter the product.
* **Integrations**: Connect different systems to exchange data and automate processes across applications.
* **Data Lake**: Store raw data from various sources—such as files, logs, and clicks—in a scalable and cost-effective way. Ideal for analytics, training AI models, and freely exploring your data.
* **Data Warehouse**: Centralize structured data to build reports, dashboards, and track KPIs with greater control and security.
* **Agent Flow**: Create interaction flows using visual elements like messages, buttons, and agents.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.skyone.cloud/english/skyone-studio/overview/quick-guide-to-skyone-studio.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.