> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/advanced-desktop/inspector-only-notes.md).

# Inspector Only Notes

What they do and how to build them.

### Inspector-Only Notes for Fast Comments and to Hide Critical Information

This is the Mullet Feature: Business in the front and party in the back.

Use this feature to build knowledge into your templates, such as codes or installation requirements that you just want for the inspector and not for the client or the finished report. This shows you how it works - the video below will show you how to build them into your template.

{% embed url="<https://youtu.be/NJaHgmQDVGY>" %}

## Building Inspector Only Notes In Your Template

{% embed url="<https://youtu.be/tLcrOaN6dlM>" %}


---

# 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.scribeware.com/advanced-desktop/inspector-only-notes.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.
