Add and upload skills
Add skills to a workspace, group them in plugins, upload Claude Code plugins, and choose the skills each agent can use.
A skill is a folder of instructions and supporting files that agents load when a task needs it. Add skills on the workspace Skills page. You can pick one from the directory, write one, or upload skills you already have, for example from Claude Code or Claude.ai. A plugin groups related skills, for example a LinkedIn plugin with its li-* skills. Every agent gets the workspace skills automatically, and you can remove any skill from one agent.
Who can do this
Workspace Owners and Admins can add, upload, edit, and delete workspace skills and plugins. Members can open the Skills page and read every skill.
Add a skill
- Open Skills in the workspace sidebar.
- Select Add, then choose one option:
- Browse skills adds a skill from the directory.
- Write a skill opens an editor for a new skill.
- Upload skills adds skills from files on your computer.
- New plugin creates a plugin. See Group skills in plugins.
A new skill reaches every agent automatically. A project gets it only when you turn it on there. See Choose an agent's skills.
Upload skills
- Select Add → Upload skills, or drag files onto the Skills page.
- Choose or drop one of these:
- A skill folder: a folder with a
SKILL.mdfile. - A folder of skills, such as
~/.claude/skills/. - A
.zipor.skillarchive. - A single
SKILL.mdfile. - A Claude Code plugin folder or
.ziparchive. See Upload a Claude Code plugin.
- A skill folder: a folder with a
- Review the list. Each row shows one skill and its state:
- New: the workspace has no skill with this name.
- Skip or Replace: a skill with this name exists. Skip is the default. Replace saves the upload as a new version, so View history keeps the old one.
- Unchanged: the upload is the same as the current version. Nothing is sent.
- A red alert icon: the skill cannot be uploaded. The reason shows under the list.
- Clear the checkbox of any skill you do not want, then select Upload skill (or Upload N skills).
When all skills upload, the dialog closes and the first skill opens. If a skill fails, the dialog stays open with the reason. Select Retry to send the failed skills again.
On a phone, use Choose files with a .zip archive or a SKILL.md file.
Group skills in plugins
A plugin is a named group of workspace skills. A skill is in one plugin or in none. The Skills page lists each plugin with its skills below it, then the skills that are not in a plugin.
- Select Add → New plugin.
- Enter a Name and an optional Description.
- Select the skills to put in the plugin. The list shows skills that are not in a plugin yet.
- Select Create plugin.
To change a plugin, select it in the list:
- Add skills puts more skills in the plugin.
- The plugin menu → Edit changes its name and description.
- The plugin menu → Delete plugin removes the plugin. Its skills stay in the workspace as standalone skills, and agents keep them.
To move one skill, open its menu. Move to plugin puts it in a plugin, or in a new one. Remove from plugin makes it a standalone skill again. Moving a skill does not change which agents use it.
Upload a Claude Code plugin
A folder or .zip archive becomes one plugin when it has a .claude-plugin/plugin.json file, or when all its skills are at skills/<name>/SKILL.md. The plugin takes its name and description from plugin.json. Without them, it takes the name of the top folder.
- Select Add → Upload skills, then choose or drop the plugin folder or archive.
- Review the list. The plugin shows at the top, with its skills below it.
- Select Upload skill (or Upload N skills). When there is nothing new to send, select Save plugin.
All uploaded skills join the plugin. If the workspace already has a plugin with the same name, the skills join that plugin. A skill that exists already joins the plugin when you choose Replace, which saves a new version, or when it shows Unchanged. A skill set to Skip stays where it is. Agents, commands, hooks, and MCP server files in the plugin are not uploaded.
If the skills upload but the plugin is not saved, the dialog shows the reason. Select Retry to save the plugin again.
Choose an agent's skills
An agent uses the platform skills and the workspace skills on its own Skills list. A new agent gets every workspace skill, and a skill that you add to the workspace later is added to every agent. This includes a skill that an agent writes in chat and you confirm. A skill that an agent learns by itself stays with that agent. If you remove a skill from an agent, it stays removed, also when the workspace adds more skills. An agent always uses the newest version of each skill on its list.
- Open the agent, then select Manage agent → Skills.
- Select Add skill. The menu lists Plugins, then Skills that are not in a plugin.
- Select a plugin to add all its skills that the agent does not have yet, or select one skill.
The list groups the agent's skills by plugin. A plugin row shows how many of its skills the agent has, for example 9 of 11. Select a skill's name to open it on the Skills page. Select X on a skill to remove it, or X on a plugin row to remove all its skills from the agent. With no workspace skills, the list shows No skills. This agent can use platform skills only.
A project uses the platform skills and only the workspace skills that you turn on in the project. A skill that you add to the workspace later is off in every project until you turn it on. A skill that an agent writes in a chat is turned on in that chat's project.
In a project, open Context → Skills. One switch on a plugin row turns all the plugin's skills on or off in the project, and the row shows how many are on, for example 1 of 11.
File requirements
Each skill needs a SKILL.md file that starts with frontmatter:
---
name: brand-voice
description: Write in our brand voice. Use for posts, emails, and replies.
---
Instructions for the agent.
namebecomes the skill name. It uses lowercase letters, numbers, and hyphens. Withoutname, the folder name is used.descriptionis required and can be up to 1,024 characters. Agents read it to decide when to load the skill.- Every other file in the folder, and in its subfolders, belongs to the skill. A
SKILL.mdin a subfolder is an ordinary file of the outer skill.
| Limit | Value |
|---|---|
SKILL.md | 128 KB |
| Any other file | 100 MB |
| Files per skill | 256 |
| Total size per skill | 100 MB |
| Files in one upload | 2,000 |
| Size of one upload, archives unpacked | 100 MB |
Text and binary files are both accepted, for example PDFs, images, fonts, decks, and templates. A text file larger than 1 MB is kept as a binary file. Upload ignores .DS_Store, __MACOSX, .git, and node_modules folders, and other hidden files. A .zip file inside a skill folder stays a file of the skill. When every file in an archive is inside one top folder, such as repo-main/, that folder is read as the root.
Binary files
Select a binary file in the skill's file list to see its name and size, and to Download it. Images show a preview. In Edit, you can add and remove binary files, but you cannot change their contents.
If it fails
- No skills found. None of the files is a
SKILL.md, or none is inside a folder with one. Choose the folder that holdsSKILL.md. - SKILL.md has no name. Add a
nameline to the frontmatter, or putSKILL.mdin a folder named after the skill. - SKILL.md has no description. Add a
descriptionline to the frontmatter, then upload the folder again. - A file or the skill is larger than 100 MB. Remove or shrink the large files, then upload again.
- The upload could not be read. The archive is damaged or protected with a password, or the upload is over the limits above.
- The current version could not be read. The skill already exists and its current version did not load. Close the dialog and upload again.