Skills give ZeroTwo reusable, task-specific workflows: a directory of instructions, resources and optional scripts. Skills you create are saved to your account, show up in Customize > Skills, and sync to the desktop app. Package them as a plugin when you want to bundle them with connectors or other pieces.
Only each skill's name and description are in context up front. The full SKILL.md loads when the skill is chosen, and bundled files are read only as needed. A skill needs a SKILL.md whose frontmatter has a kebab-case name and a description under 1,024 characters with no angle brackets. It may add scripts/, references/, assets/ and agents/zerotwo.yaml.
my-skill/
- SKILL.mdRequired: instructions + metadata
- scripts/Optional: executable code
- references/Optional: documentation
- assets/Optional: templates, resources
agents/
- zerotwo.yamlOptional: appearance and dependencies
How ZeroTwo uses skills
Invocation is explicit or implicit. Type $ to pick from skills only, / for commands and skills, or @ or the + menu for everything; ZeroTwo also loads a skill by itself when the task matches its description. Make descriptions scoped and front-loaded with the situations and phrases that should trigger them.
Create a skill
The easiest route is to ask for one. Describe the workflow to the built-in Skill Creator ($skill-creator), which drafts, validates and saves the skill. On the web and in cloud runs it saves through the manage_skill tool to your account. In the desktop app on macOS you can instead demonstrate the workflow with Add > Record a skill, covered in Record & Replay. There is no Create skill button in Customize.
To make one by hand on the desktop, add a folder with this file under your personal skills location:
--- name: skill-name description: When this skill should and should not trigger. ---
Locally created skills are available immediately.
Where local skills load from
On the desktop app ZeroTwo reads skills from these locations:
| Scope | Location |
|---|---|
| Personal | ~/.zerotwo/skills/<slug>/ |
| Project | .claude/skills/<slug>/ or .agents/skills/<slug>/ in the project |
| Managed | .system/, .platform/ and plugin folders, mirrored from your account |
Managed folders are overwritten by sync, so never edit them. A same-name copy of a managed skill in your personal location is removed the next time skills sync, so to customize one, copy it under a new name (change both the folder and the name in SKILL.md) and edit that copy. Personal and project skills you author yourself are never overwritten by sync.
Distribute skills with plugins
Skill folders suit personal and project use. To group several skills, or to ship them with connectors and MCP servers, build a plugin.
Install skills from GitHub
Ask the built-in Skill Installer ($skill-installer) to list the curated skills or install one from a GitHub repository path. It writes to your personal skills. Plugin skills arrive with their plugin instead.
Enable or disable skills
Each skill has a switch in Customize > Skills and in Settings > Plugins > Skills. Turn it off to keep the skill without using it.
Optional metadata
agents/zerotwo.yaml sets how a skill looks in the app (display name, short description, icon, color, default prompt), the connectors it expects, and its invocation policy. Setting allow_implicit_invocation: false under policy stops automatic use while an explicit $skill still works. ZeroTwo also reads agents/zerotwo.yaml when you import a skill that has one.
Best practices
Keep each skill to one job, favor instructions over scripts, write imperative steps with clear inputs and outputs, and test that the description triggers correctly.