> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/company-settings/intelligence.md). # Intelligence Configure how CRAFTSMAN INTELLIGENCE behaves for your company with company-wide instructions and shared company skills. The **Intelligence** tab in **Company Settings** is where you shape how [CRAFTSMAN INTELLIGENCE](https://help.craftsmanplus.com/intelligence/) responds in chat. It holds two sections: **Company Instructions**, standing context that applies to every conversation across your company, and **Company Skills**, reusable instructions for the tasks your company runs repeatedly. To get there, open **Company Settings** and select **Intelligence** from the left navigation. {% hint style="info" %} *Company Instructions and Company Skills can only be edited by company admins.* {% endhint %} ### Company Instructions Every company has context the AI chatbot cannot know on its own: brand rules, naming conventions, preferred workflows. Company Instructions let an admin write that context down once instead of every user re-explaining it in every conversation. Whatever is written here applies automatically to every conversation across your company and takes priority over users' personal skills. There is exactly one Company Instructions block and it is always present. To use it, type directly into the field, which reads **Insert Instructions...** while empty. Changes save automatically. Leaving the field empty is fine; empty instructions simply have no effect on conversations. ### Company Skills Where Company Instructions cover standing context, skills cover tasks. A skill is a named, reusable set of instructions for something specific your company does repeatedly, like a multi-step brief you would otherwise paste into the chat each time. Company skills are available in every conversation across your company. The chatbot sees each skill's name and description, then loads its instructions when the task calls for that skill. All company users can view skills; only company admins can add, edit, or remove them. #### **Adding a skill** Select the plus button on the **Company Skills** header to open the **New Company Skill** dialogue. Write the skill's instructions and select **Confirm**. You do not name the skill yourself; CRAFTSMAN INTELLIGENCE generates the skill's name and description from the instructions you wrote. #### **Managing skills** Each skill appears as a row showing its name, its description, and its instructions in a field below. Instructions are edited right in the row and save automatically, the same way as Company Instructions. The name and description are read only in the row. To change them, select the pencil on the row to open the **Edit Skill** dialogue, where you can rewrite the **Skill Name** and **Skill Description**. Neither field can be left empty. To delete a skill, select the minus on its row. The **Remove Skill?** confirmation names the skill you are about to delete; select **Confirm** to remove it. Deletion is permanent and cannot be undone. A company can have any number of skills. Instructions are required and cannot be saved empty or with only whitespace. Editing instructions does not regenerate the skill's name or description. --- # 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://help.craftsmanplus.com/company-settings/intelligence.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.