> ## Documentation Index > Fetch the complete documentation index at: https://trytilde.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Manage skills > Add skills from the Tilde catalog, Git, or the skill editor, and choose which skills each agent can use. You manage skills in two places. The **Skills** page holds every skill source in your installation. Each agent's **Skills** tab then picks which of them that agent uses. ## Add skills Open **Skills**. Tilde lists skills grouped by source, with each skill's description, version, and the number of agents that use it. Filter by **Catalog**, **Git**, or **Editor**. ### From the Tilde catalog Select **Tilde Catalog**. The catalog has two kinds of entry: * **Built into Tilde.** Skills that ship with Tilde, such as how to use channels, goals and tasks, and attachments. Tilde updates them when you upgrade. * **Managed provider.** Curated skills from a provider's GitHub repository, such as Anthropic, Microsoft, Cloudflare, AWS, Stripe, or Vercel. Preview a provider's skills, then select **Enable**. Tilde syncs a managed provider when you enable it, every hour, and when you select **Sync now**. ### From Git Select **Add from Git**, and enter: | Field | Value | | - | - | | **Name** | A name for the group. | | **GitHub repository URL** | `https://github.com//` | | **Branch** | Defaults to `main`. | | **Path** | Optional. Only skills under this folder are included. | Every folder with a `SKILL.md` becomes a skill, and owns the files beneath it. Tilde syncs the repository when you add it, every hour, and when you select **Sync now**. If a sync fails, Tilde shows the error on the group, and keeps the last good skills. A sync never replaces a newer commit with an older one. Tilde reads repositories with the gateway's GitHub token, so it can reach private repositories and avoid GitHub rate limits. Git sources support GitHub only. ### In the skill editor Select **Create in editor**. The editor shows the skill's files in a tree. Markdown opens in a rich text editor, and code in a code editor. You can add files and folders, upload files, rename, and delete. Edit the name and description at the top of the page. Tilde saves them to the `SKILL.md` front matter. A new name renames the skill. Changes save automatically about a second after you stop typing. Each save is the skill's next version. If someone else saved a newer version first, Tilde refuses your save and reloads the skill. Catalog, Git, and bundled skills are read-only in the editor. ## Give skills to an agent Open the agent in the Agent Registry, and select **Skills**. Select **Add skills**, then **Choose existing**, and pick a group. A new group starts switched off. Switch on the group in the **Use** column. The agent gets every skill in the group, including skills that a later sync adds. To leave out a skill, switch it off on its own row. Switching the group off and on again clears these choices. The tab also shows: * **Bundled** skills from the agent's serving deployment. They are always on. * Skills the agent receives through a connection, marked **via** that connection. Changes apply from the agent's next invocation. No redeploy is needed. ## Give skills through a connection You can link a group, or single skills, to a [connection](/docs/connections). Every agent that holds the connection's skills capability then receives them, while the connection is ready. Use this to ship instructions with an integration. For example, link a skill that explains your ticket conventions to your Linear connection. On the **Skills** page, open a group's actions, select **Connections**, then **Link connection**. ## Share, sync, and delete groups Each group's row on the **Skills** page has these actions: * **Share** grants other people access to the group, in Tilde Cloud and Tilde Enterprise. * **Sync now** pulls the latest skills of a catalog or Git group. * **Connections** links the group to connections. * **Delete group** removes the group and its skills from every agent. ## Who can manage skills CLOUDENTERPRISE Tilde Cloud and Tilde Enterprise control skill management with [operator roles](/docs/operator-access). Each group has its own reader and editor roles, and whoever adds a group becomes its editor. | Action | Needs | | - | - | | Add a group | Any signed-in user. A management API key needs `edit` on every group. | | Edit, sync, or delete a group or its skills | `edit` on the group. | | Give an agent skills | `edit_skills` on the agent, and `view` on the group. | | Remove skills from an agent | `edit_skills` on the agent. | | Link a group to a connection | `view` on the group. | ## Agent capabilities for skills Grant these on an agent's **Capabilities** tab. See [IAM](/docs/iam#capability-reference). | Capability | Targets | Lets the agent | | - | - | - | | `agents.edit_skills` | Agents | Assign and unassign skills on the selected agents, itself included. | | `skills.read` | Skill groups | See the selected groups, and assign their skills. | | `skills.edit` | Skill groups | Write skills into the selected editor groups, and sync Git and catalog groups. Includes `skills.read`. | An agent can always read its own skills. To read another agent's skills, it needs `agents.read`. In Tilde Cloud and Tilde Enterprise, you can grant `skills.read` or `skills.edit` only on groups you can view. An agent never reaches a group its granter cannot see.