> For the complete documentation index, see [llms.txt](https://jembi.gitbook.io/instant-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jembi.gitbook.io/instant-v2/package/adding-your-package.md).

# Adding your package

Packages can be added in tow different ways. These are described below.

## Using a custom package config

You may define custom packages either in the [config file](/instant-v2/getting-started/config.md) or via a [command line flag](/instant-v2/getting-started/cli.md). This configuration can either be a **local path** to the package or a **github url**.

## In a custom docker image

Packages can be built into a custom docker image that you may version and push to Docker Hub as you wish. This is the image referenced in the `image` property of the config file. This image MUST be built by extending the `openhie/package-base` package which contains some key dependencies. See an example of how Jembi does this [for Jembi Platform here](https://github.com/jembi/platform/blob/main/Dockerfile#L1-L3). You simple need to add your package folder into the image.


---

# 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://jembi.gitbook.io/instant-v2/package/adding-your-package.md?ask=<question>&goal=<user_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.