> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/2d-building/building/levels/roof-geometry/add-skylights.md).
# Add Skylights
A skylight refers to a window that is placed on the roof of a building. It is a specific type of "fenestration surface" that generally includes all areas in the building's exterior, like windows, doors, and skylights, that let in light.
## Add a Skylight
To draw a Skylight, we first need to have drawn a Roof. Next, select 'Levels' on the left side and locate any Level with a Roof. Now, left-click any 'Edit Zone'. In the drawing ribbon, select 'Add Skylights' and then draw the dimensions of the skylight. Your Skylight specification is always nominated under the Envelope settings for Skylights.
{% hint style="danger" %}
Skylights must be directly above a Zone and cannot be above two Zones, crossing an internal wall. It is generally ok to add up to five Skylights per zone. A roof may need to be split into multiple roofs to add more than five skylights.
{% 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://docs.betterbuilding.io/user-guide/2d-building/building/levels/roof-geometry/add-skylights.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.
