Create and edit a skill
Write the instructions once, name them clearly and decide who can use them.
Write a skill
- Open Settings → Plugins → Skills and select Add skill.
- Enter a Name and a one-line Description that says when the skill applies.
- Write the instructions in Content as Markdown.
- Open Skill settings below the body and set Show to agent automatically.
- Administrators also pick Visible to: Only me or Everyone.
- Select Save skill.
The name uses lowercase letters, digits and dashes, up to 64 characters, for example deploy-checklist. The same name becomes the file name, so keep it short and descriptive.
Names and scopes
A name must be unique across the skills a session can see. A personal skill cannot take a bundled or instance-wide name, and an instance-wide skill cannot take a name that any account already uses for a personal skill.
Creating a personal skill with a name you already use updates that skill, and writing a name that exists in the same set replaces its file. Bundled skills are read only.
A personal skill appears only in its owner's conversations. An instance skill is shared across the installation and needs administrator authority to create or change in the manager. Changing Visible to moves the skill file to the other set.
Supporting files
A custom skill is either a single Markdown file or a folder containing SKILL.md. A skill with extra material, such as a template or a checklist, needs the folder form.
SkillLoad names the skill's folder, and Read opens a supporting file by its path there.
Save and conflicts
Save skill writes the scope, the description, the body and the automatic switch together. The plugin page and its Settings section share one editor.
If the skill changed since you opened it, the save is refused until you reload it.
The Skill settings group starts closed and remembers your choice in this browser, separately for each surface, account and skill. The skill list keeps its own automatic-use switch, and changing the draft's scope keeps the group remembered because that memory is keyed to the skill's original owner.
Delete a skill
Select Delete skill in the manager, or the delete action in the /skills picker. Deleting a skill that lives in a folder keeps its supporting files.
In the terminal picker you confirm the deletion. If the owner changes before you confirm, select the skill again.
Use ListSkills to check the exact name before DeleteSkill. Deleting is permanent, so a skill you may want back is better left manual than deleted.
Create a skill from chat
CreateSkill saves a skill for later conversations and requires a scope of personal or instance. Only the instance owner can write instance-wide skills through the tool, while the manager accepts instance-wide writes from administrators.
When an account is deleted, its personal skills go with it.