> For the complete documentation index, see [llms.txt](https://guide.scribe.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.scribe.gov.sg/guides/view-your-default-overview.md).

# View your Default Overview

Scribe automatically generates a Default Overview for every session once it has been processed. 

The Default Overview gives you a high-level summary of the conversation and is differentiated from your other summaries by its banner.

<figure><img src="https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2FRKPr7mEy5xpaeD2t2EAY%2Fimage.png?alt=media&amp;token=55b1721f-db89-4a6f-9fa6-153cbf05fb89" alt="" width="563"><figcaption></figcaption></figure>

#### **What's included in the Default Overview?**

<table><thead><tr><th width="209.935791015625">Section</th><th>What it is</th></tr></thead><tbody><tr><td>High-level Overview</td><td>A quick breakdown of your conversation, including key observations, decisions made during the conversation and any follow-up actions for parties in the conversation</td></tr><tr><td>Topics Discussed</td><td>A list of the key topics discussed in the conversation, with a quick summary of each topic's details</td></tr></tbody></table>

#### **The Default Overview is useful for:**

* A quick reference of what was discussed
* A first draft for your documentation
* Ideas for section headers when you create your own summaries

{% hint style="info" %}
The Default Overview always has the same structure and format. To customise your summaries, try [Generate Summaries](/guides/generate-summaries.md) instead.
{% endhint %}


---

# 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://guide.scribe.gov.sg/guides/view-your-default-overview.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.