> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/6.1/user-guide/schemas.md).
# Schemas
This page describes how to manage Schema in a Schema Registry with Lenses.
{% hint style="success" %}
To delete schemas you need to enable **`lenses.schema.registry.delete`** in **lenses.conf** of the agent.
{% endhint %}
## View schemas
Go to SQL Studio, navigate to the environment you want to view schemas for in the tree,
## Creating schemas
To create a new schema, select **SQL Studio,** on the Schema node, click open in tab.
## Viewing schemas
EIther select the schema from the schema listing or expand the node in the tree view explorer and select the topic.
You can also use the breadcrumbs at the top of the tab to navigate to different schemas.
## Editing schemas
To edit a schema select either the key or value schema, click Edit to change the schema.
---
# 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.lenses.io/latest/devx/6.1/user-guide/schemas.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.
