Skills
Managing skills
For admins: import skills, switch them on and off, set run limits and keys, and remove them.
# Managing skills The skills page is for admins only. Select **Skills** in the top bar to open it. ## The page Every skill is a card in the order of the tree's departments. The card shows the skill's icon in its department's colour, an on and off switch and a settings dropdown. A skill that cannot run yet carries a **Needs setup** badge under its switch. Use **Search skills** to find one and the **Show** filter (**All**, **On**, **Off**) to narrow the list. The department chips under them (**All**, then each department that has skills, with its count) show one department at a time. Select a card to open the skill: its department and team, its full description, whether it runs, needs setup (and what it is missing) or is switched off, and **Start** for a skill that is on and ready. The switch and the settings dropdown on a card work without opening it. The open card also lists the skill's **History**, and **Edit Skill** opens its editor; see [Changing a skill](https://docs.skilltreeos.ai/skills/changing-a-skill/). A skill that is switched off is left out of what the brain can use. ## Importing a skill Select **Import a Skill** and choose a `.zip` or `.md` file. The brain reads it and shows a review: the title, the description, how many files it holds, any tools this workspace lacks, and the keys it names. If a skill with that name exists, the review says **Replaces version** and its number. Pick the **Department**, **Team** and, if it fills one, the roadmap job under **Fills roadmap job**, then select **Import**. Managed skills, those Altari or your team's repository ships, cannot be replaced by an upload. Members can make skills too. See [Making a skill](https://docs.skilltreeos.ai/skills/making-a-skill/). ## The settings dropdown Select the dropdown on a card to see its version and where it came from, and any **Needs setup** notes, for instance that it names a key you have not stored. For skills that run scripts, two settings appear: - **Run time limit**: how long one run may take. Use a whole number of seconds from 10 to 840. Empty means the default of 2 minutes. - **Keys it receives**: names of stored keys, separated by commas. A run gets only the keys named here. Skills that work inside the chat show no run settings. ## API keys for skills The same page holds **API keys for skills**. Add a name in capital letters, digits and underscores (for example `KEY_NAME`) and its value. Keys are stored encrypted, shown only as set or unset, and a skill receives only the names it lists. Use restricted keys where a service offers them. A note appears if skill keys are not set up on the deployment. ## Removing a skill Skills made or imported by hand have **Remove Skill** in the dropdown. The dialog **Remove a skill** reminds you that chats that ran it stay, as ordinary chats. A managed skill has no remove button while Altari or your team's repository still ships it. Switch it off instead. ## Shaping the tree Departments and teams are edited on the tree, not here. See [Editing the tree](https://docs.skilltreeos.ai/skill-tree/editing-the-tree/). The bundles that install skills automatically are described in Skill bundles.The skills page is for admins only. Select Skills in the top bar to open it.
The page
Section titled “The page”Every skill is a card in the order of the tree’s departments. The card shows the skill’s icon in its department’s colour, an on and off switch and a settings dropdown. A skill that cannot run yet carries a Needs setup badge under its switch. Use Search skills to find one and the Show filter (All, On, Off) to narrow the list. The department chips under them (All, then each department that has skills, with its count) show one department at a time.
Select a card to open the skill: its department and team, its full description, whether it runs, needs setup (and what it is missing) or is switched off, and Start for a skill that is on and ready. The switch and the settings dropdown on a card work without opening it. The open card also lists the skill’s History, and Edit Skill opens its editor; see Changing a skill.
A skill that is switched off is left out of what the brain can use.
Importing a skill
Section titled “Importing a skill”Select Import a Skill and choose a .zip or .md file. The brain reads it and shows a review: the title, the description, how many files it holds, any tools this workspace lacks, and the keys it names. If a skill with that name exists, the review says Replaces version and its number.
Pick the Department, Team and, if it fills one, the roadmap job under Fills roadmap job, then select Import. Managed skills, those Altari or your team’s repository ships, cannot be replaced by an upload.
Members can make skills too. See Making a skill.
The settings dropdown
Section titled “The settings dropdown”Select the dropdown on a card to see its version and where it came from, and any Needs setup notes, for instance that it names a key you have not stored.
For skills that run scripts, two settings appear:
- Run time limit: how long one run may take. Use a whole number of seconds from 10 to 840. Empty means the default of 2 minutes.
- Keys it receives: names of stored keys, separated by commas. A run gets only the keys named here.
Skills that work inside the chat show no run settings.
API keys for skills
Section titled “API keys for skills”The same page holds API keys for skills. Add a name in capital letters, digits and underscores (for example KEY_NAME) and its value. Keys are stored encrypted, shown only as set or unset, and a skill receives only the names it lists. Use restricted keys where a service offers them. A note appears if skill keys are not set up on the deployment.
Removing a skill
Section titled “Removing a skill”Skills made or imported by hand have Remove Skill in the dropdown. The dialog Remove a skill reminds you that chats that ran it stay, as ordinary chats.
A managed skill has no remove button while Altari or your team’s repository still ships it. Switch it off instead.
Shaping the tree
Section titled “Shaping the tree”Departments and teams are edited on the tree, not here. See Editing the tree. The bundles that install skills automatically are described in Skill bundles.