> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/template-editor/miscellaneous/custom.md).
# Custom
### 
This is a library of custom widgets created by WEM and by partners of WEM. This library grows continuously and has a lot of different widgets. When you drag the rocket to your template you get prompted to select the widget you want to add.
\
The first time you do this there are probably not many widgets listed, and you need add a library first. Select the 'Add more widgets here' link and select a library you want to add to your account. Take a look around here. There are a lot of different widgets and every one is for a different use-case.
There is also a place dedicated to managing [Widget Libraries](/platform/wemmodeler/files-and-assets/widget-libraries.md). Some widgets specific explanation can be found in the [Widgets](/platform/wemtipsandtricks/widgets.md)folder.
{% hint style="info" %}
Global widgets are reviewed and monitored by WEM for security vulnerabilities.\
Custom-built widgets or external widgets (for example, from third-party libraries) fall under the developers own responsibility. These are **not** security-checked by us and may contain unsafe or malicious code.
{% 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.wem.io/platform/template-editor/miscellaneous/custom.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.
