Skills
What a skill is
What a skill contains, where skills come from and how the brain picks one up.
# What a skill is A skill is a folder with a file called `SKILL.md` and, if needed, other files. `SKILL.md` holds a name, a description and the instructions the brain follows. Other files can be templates, examples or scripts. ## Where skills sit Every skill lives on the skill tree, in a team inside a department. It can fill a roadmap job that was waiting for it, or stand as a new leaf. See [Departments, teams and jobs](https://docs.skilltreeos.ai/skill-tree/departments-teams-and-jobs/). ## Where skills come from - **Made by you or a colleague** with the skill maker. See [Making a skill](https://docs.skilltreeos.ai/skills/making-a-skill/). - **Imported by an admin** from a file. See [Managing skills](https://docs.skilltreeos.ai/skills/managing-skills/). - **Shipped by Altari.** These are generic skills that arrive with the platform and update by themselves. An update keeps the admin's on and off setting and the skill's place on the tree. - **From your team's skill repository.** Some companies keep their own skills in their repository. They are installed the same way. Skills that Altari ships or your team's repository ships are managed. An upload cannot replace them. An admin can switch them off, but cannot remove them while they are still shipped. ## How the brain uses a skill When you start a skill from the tree, the chat is locked to it: the brain sees its full instructions. In an ordinary chat, the brain also sees a short index of the skills that are switched on and that you may use. It can load one by itself when your question fits. The **Used** list under its answer then names the skill. See [Asking and answers](https://docs.skilltreeos.ai/chats/asking-and-answers/). A skill can say what it needs before it starts. See [Skill chats](https://docs.skilltreeos.ai/skills/skill-chats/). ## Skills that run scripts Some skills run commands, for example to build a spreadsheet. They run in a separate, isolated sandbox that your deployment has to switch on. A run can only use the keys its skill lists by name, and files it leaves in its output folder reach you as downloads. See [Files from a chat](https://docs.skilltreeos.ai/chats/files-from-a-chat/). ## What you can see You see the switched-on skills in the departments you may use. An admin who restricts your departments restricts your skills with them.A skill is a folder with a file called SKILL.md and, if needed, other files. SKILL.md holds a name, a description and the instructions the brain follows. Other files can be templates, examples or scripts.
Where skills sit
Section titled “Where skills sit”Every skill lives on the skill tree, in a team inside a department. It can fill a roadmap job that was waiting for it, or stand as a new leaf. See Departments, teams and jobs.
Where skills come from
Section titled “Where skills come from”- Made by you or a colleague with the skill maker. See Making a skill.
- Imported by an admin from a file. See Managing skills.
- Shipped by Altari. These are generic skills that arrive with the platform and update by themselves. An update keeps the admin’s on and off setting and the skill’s place on the tree.
- From your team’s skill repository. Some companies keep their own skills in their repository. They are installed the same way.
Skills that Altari ships or your team’s repository ships are managed. An upload cannot replace them. An admin can switch them off, but cannot remove them while they are still shipped.
How the brain uses a skill
Section titled “How the brain uses a skill”When you start a skill from the tree, the chat is locked to it: the brain sees its full instructions. In an ordinary chat, the brain also sees a short index of the skills that are switched on and that you may use. It can load one by itself when your question fits. The Used list under its answer then names the skill. See Asking and answers.
A skill can say what it needs before it starts. See Skill chats.
Skills that run scripts
Section titled “Skills that run scripts”Some skills run commands, for example to build a spreadsheet. They run in a separate, isolated sandbox that your deployment has to switch on. A run can only use the keys its skill lists by name, and files it leaves in its output folder reach you as downloads. See Files from a chat.
What you can see
Section titled “What you can see”You see the switched-on skills in the departments you may use. An admin who restricts your departments restricts your skills with them.