> ## Documentation Index > Fetch the complete documentation index at: https://docs.vybe.build/llms.txt > Use this file to discover all available pages before exploring further. # Knowledge, memory and skills > Give AI coworkers lasting context with notes, reusable procedures with skills, and reference files An AI coworker remembers what it learns. Its **Knowledge** section holds three kinds of memory: **Notes** for facts and context, **Skills** for step-by-step procedures, and **Files** for documents. You can add to them yourself, ask the coworker to save something, or let it learn on its own from conversations and public Slack channels. ## What goes where | Put it in | Use it for | Example | | - | - | - | | [AGENTS.md](https://docs.vybe.build/coworkers/instructions.md) | Who the coworker is and rules it always follows | "You're the support lead's assistant. Never promise refunds." | | Notes | Facts and context it should remember | "Our fiscal year starts on February 1." | | Skills | A procedure for a specific, repeatable task | "How to prepare the weekly pipeline report" | | Files | Reference documents and data | A price list PDF, last year's sales spreadsheet | AGENTS.md goes with every request, so keep it short. Notes and skills are looked up only when they're relevant, so they can hold much more. ## Notes Open the coworker and go to **Knowledge → Notes**. The list shows the notes saved from this coworker and your organization notes. Filter by note type, sort, or search. ### Who uses a note Every note has a scope. The scope decides which coworkers use it. | Scope | Shown in the editor as | Used by | | - | - | - | | AI coworker note | "Note that *name* should remember" | Only this coworker | | User note | "Note for your agents about yourself or one of your teammates" | Every coworker, but only when it's talking to that person | | Organization note | "Note that should be shared across your agents" | Every coworker in your organization | Use user notes for personal preferences, such as "Maria wants summaries as bullet points." Use organization notes for company facts that every coworker should know. Everyone who can access a coworker can see its notes. See [Sharing and access](https://docs.vybe.build/coworkers/sharing-and-access.md). ### Add or edit a note **1. Create the note** In **Knowledge → Notes**, click **Add note**. **2. Write it** Give it a title and write the content. Changes save automatically. **3. Pick the scope** Use the selector at the top of the note to choose **AI coworker note**, **User note** or **Organization note**. For a user note, also pick the person it's about. **4. Add labels and links (optional)** Add labels to group related notes. To link to another note or skill, type `@` and pick it from the list. You can also just tell the coworker in chat or Slack: > Remember that our fiscal year starts on February 1. You'll see a step like "Created note: Fiscal year" in the conversation. When the coworker reads a note while working, you'll see "Read note: …". ### History, locking and deleting Open a note and use its **…** menu: * **View history** shows earlier versions of the note, each labelled with who made the change, such as **Manual edit**, **Agent edit** or **Memory Curator**. Vybe keeps the last 50 versions. Pick one to restore it. * **Lock** freezes the note so the coworker can't change it ("Locked: the agent cannot edit this note"). Lock notes you curate by hand. To edit a locked note yourself, **Unlock** it first. * **Delete** removes the note. It isn't offered for locked notes (unlock first) or for system notes. ### System notes Some notes are managed by Vybe. AGENTS.md is one of them, and it always appears in **Notes**. See [Instructions](https://docs.vybe.build/coworkers/instructions.md). Other system notes are hidden. Turn on **Show system notes (N)** to see them. You can't delete system notes. ## Skills A skill is a reusable procedure: how to do one specific task, step by step. Notes say what's true; skills say how to do something. Each skill has a description that says when to use it. Coworkers read the descriptions and load a skill when a task matches. You'll see "Loaded skill: *name*" in the conversation. When it ends with **(automatic)**, Vybe loaded the skill for that message before the coworker replied. ### Add a skill **1. Create the skill** Go to **Knowledge → Skills** and click **Add skill**. **2. Name and describe it** Give it a clear title and a description. The description is required ("Description cannot be empty for skills"). Write it as a trigger, for example "Use when someone asks for the weekly pipeline report." **3. Write the steps** List the steps the coworker should follow, the sources it should use, and what the result should look like. **4. Pick the scope** Use the selector at the top of the skill to choose **Agent skill** ("Skill that *name* should use"), **User skill** ("Skill for your agents when helping you or one of your teammates") or **Organization skill** ("Skill that should be shared across your agents"). A skill can also set a **Model**. Leave it on **Inherit agent model** for everyday skills. For a hard procedure, pin a more capable model and effort: when the coworker loads the skill, it switches to that model for the rest of its current reply. Skills have the same **…** menu as notes: **View history**, **Lock** and **Delete**. ### Let coworkers write skills Coworkers can save a procedure as a skill on their own, or when you ask: > That worked well. Save how you built this report as a skill so you can do it again next week. Coworkers can create and update skills, but they can't delete them. Coworkers also have built-in skills from Vybe. These don't appear in your **Skills** list, but you may see them in "Loaded skill" steps. ## Files **Knowledge → Files** is the coworker's own file storage. It's the same storage the coworker uses for its work, so files it creates show up here, and files you add are there for it to use. * Click **Add file** to upload one or more files, up to 4.1 MB each. * Open folders to browse, click a file to preview it, and download it from the list or the preview. The **Files** tab is hidden when the coworker's **Files** capability is set to **Off**. See [Capabilities](https://docs.vybe.build/coworkers/capabilities.md). ## How coworkers learn on their own ### Automatic memory **Curate memory automatically** is on by default. After each conversation, it "saves lasting knowledge and removes outdated facts." Turn it off in **Knowledge → Notes** to pause automatic learning, including learning from Slack. Notes you add yourself, and notes the coworker saves when you ask, still work. ### Learning from Slack Coworkers in Slack also learn from public channels they belong to, without being mentioned. This includes thread replies. Vybe reviews a thread once it has gone quiet for a few minutes. It saves only lasting knowledge, picks which coworkers in the channel should learn from it based on their roles, and decides whether a fact belongs in a coworker's own notes or in organization notes. Slack memory never uses: * Private channels * Direct messages and group DMs * Slack Connect channels * Messages from guests, or from anyone who isn't a full member of your Slack workspace Facts that come from another AI coworker are saved with a warning, "Reported by agent *name*. Treat with caution, and check the thread to see whether people agreed." Facts from other Slack bots start with "Reported by a Slack bot:". There are two controls: | Control | Where | What it does | | - | - | - | | **Learn from Slack** | Coworker → **Knowledge → Notes** | Turns Slack learning on or off for this coworker. On by default. Needs **Curate memory automatically** to be on. | | **Slack memory** | **Settings → Organization → General** (Owners and Admins) | Turns Slack learning on or off for the whole organization. On by default. | Under **Slack memory**, Owners and Admins can also set the **Minimum usefulness score**, from **More inclusive** to **More selective** (default 0.70). Threads that score below it are ignored. Four tabs hold the instructions Vybe follows: **What to remember**, **Finding notes and skills**, **Choosing agents** and **Curating memory**. Click **Save changes** to apply them, or **Discard changes**. ### The ingestion log To see what a coworker learned and where it came from, go to **Knowledge → Notes** and click **View ingestion log**. The **Ingestion log** lists "Memory changes and reviewed Slack messages, newest first." Each entry shows: * What happened, such as **Created note**, **Appended**, **Modified**, **Merged**, **Ignored** or **Conflict**. Ignored threads and settled contradictions are listed too. * The source: **Slack**, **Agent conversation**, **Memory curator**, **Manual**, **API** or **Restored version**. * Whose memory changed: **Agent memory**, **User memory** or **Organization memory**. * **Open in Slack** for entries that came from Slack, and **Open activity** to see the run behind the change. Search with "Search notes, changes or messages…", filter by source, and click **Load older entries** to go further back. **Recover past history** rebuilds entries from saved note versions. It can't bring back deleted notes. The log doesn't keep a copy of Slack messages. Vybe fetches them from Slack when you open an entry, so a deleted message shows as deleted. ## The Knowledge page **Knowledge** in the main sidebar is "Organization memory — notes, skills, and files in one place." Its **Notes** and **Skills** tabs combine organization notes, user notes and the notes of every coworker you can access. * Filter by note type: **All note types**, **AI coworker notes**, **Organization notes** or **User notes**. * Filter by coworker, or choose **All AI coworkers**. * Sort, or search titles and content. * Click a note or skill to open it. You can't add organization notes from this page. Add them from any coworker's **Knowledge → Notes**. ## Tips * **One topic per note.** Short, focused notes are easier for coworkers to find and keep up to date. * **Write skill descriptions as triggers.** "Use when…" tells the coworker exactly when the skill applies. * **Share company facts once.** Make them organization notes so every coworker benefits. * **Lock what you curate.** Lock notes you maintain by hand so automatic memory doesn't rewrite them. * **Fix wrong memories at the source.** If a coworker keeps repeating something wrong, check the ingestion log, then edit or delete the note. * **Keep secrets out.** Don't store passwords or API keys in notes or files. [Connect the tool](https://docs.vybe.build/connections/overview.md) instead. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.