> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/agent/agent-library.md). # Library Give Agent reusable methods and reference material with skills and documents. The [Library](https://app.cogram.com/dashboard/agent/library) holds reusable **Skills** and **Documents**. Scope decides who can see and manage each item. ## Skills A skill is a reusable procedure. Its description tells Agent when to use it. Its instructions define the inputs, method, evidence, output, and limits. To create one, open **Library → Skills**, choose **Personal**, and select **Create skill**. Use a lowercase name with letters, numbers, and hyphens. Organization admins and owners can create an **Organization** skill. They can also promote one of their personal skills for organization use. ## Documents A Library document is standing reference material, such as a firm standard, checklist, approved proposal text, or sample deliverable. Open **Library → Documents** and choose a scope before upload: | Scope | Who can read it | Who can manage it | | ---------------- | -------------------------- | ---------------------------------- | | **Personal** | Uploader | Uploader | | **Project** | Authorized project members | Users with project file permission | | **Organization** | Organization members | Organization admins and owners | Project Agent documents are available to authorized project members. They do not appear in the project's document register. Ordinary files in the project **Documents** area also become available in project-scoped Agent work. Deleting a Library document removes it from future work. It does not change completed chats or runs. ## How Agent uses Library items The General Cogram assistant can use your personal and organization Library items. In project context, it can also use project Agent documents and ordinary project documents. A specialist Agent uses the skills and documents attached to its configuration. It can also search project data when the chat or Automation has project context. Open a specialist Agent's **Library** tab to review its attached items. If you can configure the Agent, you can add an existing item or create one there. These attachment rules protect private material: * A private Agent can attach its owner's personal items and organization items. * A shared personal Agent can attach organization items only. * An Organization Agent can attach organization items only. * Project items stay with their project and cannot be attached to a specialist Agent. Attaching an item does not copy it. Later edits apply to future chats and Automation runs. ## Automations and documents A personal Automation can select personal or organization Library documents. Documents attached to its specialist Agent are included automatically. Project documents are found through the Automation's project scope. ## Prepare useful content Keep a skill's description specific. In its instructions, define the required inputs, work sequence, citations, output, and stopping conditions. Use approved, current documents. Include an owner, effective date, and revision where possible. Remove obsolete material rather than leaving conflicting versions available. Do not place project-restricted or personal material in an organization item. ## Check sources Ask Agent to cite the skill, document, section, page, revision, or source record behind an important statement. Check the source before relying on technical, commercial, code, or contractual output. ## Troubleshooting **I cannot add a personal item to a shared Agent** Shared Agents cannot use personal Library items. Keep the Agent private or ask an admin to create an organization version. **A project document is missing from the Agent selector** Project documents cannot be attached to a specialist Agent. Select the project as chat or Automation context. **Agent does not use a skill** Make its description more specific, or attach it to the specialist Agent. ## Next steps * [Specialist Agents](/agent/agents.md) * [Agent](/agent/agent.md) * [Automations](/agent/automations.md) --- # 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.cogram.com/agent/agent-library.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.