> For the complete documentation index, see [llms.txt](https://eirin-ai.gitbook.io/eirin-ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/knowledge-base.md). # Knowledge base Give Eirin your game's FAQ, patch notes and game bible so it answers players from your own material, not guesswork. Every community manager has its own **Knowledge** tab: the material it answers players from when it drafts a reply. Add your game's FAQ, patch notes and game bible there, and Eirin grounds its replies on your facts. Edits apply to the very next reply. {% hint style="info" %} **Knowledge is per agent and Eirin-only.** Game 1's knowledge never reaches Game 2, and nothing here is shared with any other tool. {% endhint %} ## The four sections Open the agent's profile and click **Knowledge**. Four cards at the top show how many entries each section holds: ![The Knowledge tab before anything is added](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-835efceaa820d222581dfa26eaa78b8d6c891fa4%2F27_Profile_knowledge.png?alt=media) | Section | What goes here | How a document is split | | --------------------- | -------------------------------------------- | ------------------------------------- | | **Game FAQ** | Player questions and their canonical answers | One entry per question and answer | | **Patch Notes** | What shipped in each release | One entry per version, with its date | | **Game Bible** | Mechanics, modes, currencies, lore | One entry per heading or topic | | **Other Information** | Anything else worth answering from | Chunks, titled by heading or filename | Below the cards, **Everything, what {name} answers from** lists every entry, newest first. Click a section card to filter to that section, or type in **Search what the agent knows…**. Each entry shows its section, who wrote it, a pencil to edit and a bin to remove. ![The Knowledge tab, with one entry and its source document](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-6ddc293259ab334197bc1a4bd9a66ad0bd2821c5%2F53_Knowledge_entries.png?alt=media) ## How to add knowledge Click **Add knowledge**. Pick the section, then choose how to add: {% stepper %} {% step %} ### Upload a file **Upload file** → **Choose a file**. Supported: PDF, DOC, DOCX, TXT, MD and CSV. Eirin extracts the text and splits it into entries for the section you picked, so an FAQ document becomes one entry per question. The file is listed under **Source documents**, and it becomes answer material within minutes. {% endstep %} {% step %} ### Write it by hand **Write a Q\&A** (for Game FAQ): type the question and the answer exactly as you would tell a player, then click **Add**. For Patch Notes the option is **New version**: give the version, the release date and kind, and what changed. For Game Bible and Other Information it is **Write an entry**: a title and the details. Hand-written entries are saved as written, with no parsing, and a later file upload never overwrites them. ![Writing a Q\&A by hand](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-79e7dad020beb4bf77e2c800535d70126d41baa9%2F52_Knowledge_write-qa.png?alt=media) {% endstep %} {% step %} ### Paste text or link a document **Paste text**: paste the content and give it a name, for example "Patch 2.3 notes". **Link a doc**: paste a public Google Doc link (shared as "anyone with the link") or any public text URL. Both are split into entries the same way as an upload. ![Linking a public document](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-63b4b8b04a4dcefdb5f3b84dd02258ab0d933bf0%2F55_Knowledge_link-doc.png?alt=media) {% endstep %} {% endstepper %} If your agent has a work email, you can also email it documents as attachments. ## Editing and removing * Click the pencil on an entry to edit its title or content, then **Save**. The entry is marked **edited**: your version is kept even if the source document is uploaded again. * Click the bin to remove one entry. The rest of its document stays. * Under **Source documents**, click **Remove** to retire a whole document and every entry that came from it. ![Editing an entry in place](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-01574492a88a03a33bb53d9e7907468b72d3e72e%2F54_Knowledge_edit-entry.png?alt=media) ## How Eirin uses it When Eirin drafts a reply, it looks up the entries that match the review or comment and writes from them. In the reply queue, a draft that used your knowledge shows **Grounded on** with the entries it relied on, so you can see where a fact came from before you approve. See [Approve and post replies](/eirin-ai-docs/working-with-eirin/approve-and-post-replies.md). Good material to add: {% columns %} {% column %} * Community FAQ, support macros * Release notes and patch history * Known issues and planned fixes {% endcolumn %} {% column %} * Game design document or feature list * Lore and story docs, if players ask about them * Platform and account facts (where to buy, how to link accounts) {% endcolumn %} {% endcolumns %} {% hint style="success" %} **After every release,** add the new patch notes. They become answer material within minutes, so outdated complaints are answered with the fix that shipped. {% endhint %} ## Knowledge vs. voice Eirin learns two different things, from two different places: | | What Eirin learns | Where from | | ------------- | -------------------------------------------------------- | ---------------------------------------------- | | **Voice** | Your studio's tone and how it talks to players | Your team's past replies, and your reply rules | | **Knowledge** | Facts about your game: mechanics, releases, known issues | The Knowledge tab | ## What's coming | Capability | What it does | Status | | ---------------------- | --------------------------------------------------- | ------------ | | **Google Drive sync** | Keep a Drive folder in sync with the knowledge base | Planned | | **Self-learning loop** | Gets sharper with every approval and edit | In the works | --- # 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://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/knowledge-base.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.