> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/knowledge-base/gaps.md).
# Gaps
Discover gaps in your documentation
## Issues
Pylon helps enable you to run an effective "Knowledge-centered Support" or [KCS process](https://en.wikipedia.org/wiki/Knowledge-centered_support). When solving any issue, you can quickly mark it as needing an article from the Issue Sidebar.
Marked issues show up in a queue on the Gaps page, allowing you to use [Copilot](/pylon-docs/knowledge-base/articles-and-collections/copilot.md#article-generation) to quickly create missing articles.
## Topics
Pylon will autogenerate topics for common questions you receive that are not covered by your connected documentation. To help you target your efforts in the highest impact areas, AI will highlight the most common missing topics.
* Merge, delete, or edit topics to help improve the AI
* Used the shared context of all issues on a topic to create new articles with [Copilot](/pylon-docs/knowledge-base/articles-and-collections/copilot.md#article-generation)
* Click into a topic to browse the summary of the gap, resources, and issues associated with it
---
# 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.usepylon.com/pylon-docs/knowledge-base/gaps.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.
