> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/content-library/runbooksdb/creating-a-repository.md).
# Creating a Repository
Step 1: From the **Repositories** tab of the **RunbooksDB** module, click **New Repository**.
Step 2: Enter information in the fields and select the desired security access for the repository.
1. **Repository Name**: Describes the repository and is displayed on the repository card from the **Repositories** tab.
2. **Writeup ID Prefix**: A three-character value that is unique to this repository. An error message will display if the prefix already exists after clicking the **Create** button in Step 3.\
3. **Description**: Describes the repository.
4. **Repository Access**: Defines what [users and roles can access](/plextrac-documentation/product-documentation/content-library/types-of-repositories.md) the writeups in this repository.
Step 3: Click **Create**.
The new repository now has a card on the **Repositories** tab.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation/content-library/runbooksdb/creating-a-repository.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.