Skills
Skill is the older name for what your workspace now calls a workflow: a named, reusable procedure that teaches Zero how your team does a specific kind of work. Same concept, current name.
If you landed here looking for how to capture a repeated prompt, share it with your team, or run it on a cadence, Workflows is the page you want.
What changed
| You may have read | The current name |
|---|---|
| Skill | Workflow — created, edited, copied, and shared from the Workflows page |
| Skills are workspace-scoped and shared automatically | Every workflow belongs to one agent and is either private or public to the workspace. Sharing is a choice you make, not a side effect of saving. |
/slash-command invocation, with a visual picker "on the roadmap" | Workflows are listed in the workspace and can be invoked by name in plain language. Zero also loads one automatically when the request matches its description. |
| Schedule | Automation — a trigger attached to a workflow. Cadence is one trigger type among many; see Schedules. |
Where the word still appears
- Built-in skills. Every agent ships with a roster of cross-functional procedures maintained by VM0 — research, finance, legal, product, marketing, support, and team communication. They behave exactly like the workflows you write. The current list is on Workflows.
SKILL.md. When a workflow is packaged with supplementary files, the procedure is expressed as aSKILL.mddocument generated from the workflow's name, description, and instruction. You don't write this file yourself.
What's next
- Workflows — the full guide: anatomy, ownership, visibility, and how Zero picks one.
- Automations — schedules, email, GitHub, calendar, Notion, and webhook triggers.
- Agents — who runs a workflow, and with which connectors.