Skills
Create, review, version and use shared instruction packages
A skill packages instructions for a recurring task. Its main file, SKILL.md, names the skill, explains when it is useful and describes how to do the job. Supporting files can contain checklists, examples and reference material.
For example, an equipment-risk review skill can require checking evidence dates before interpreting a failure prediction. The skill supplies the review procedure. The forecaster produces the prediction, a query supplies evidence, and permissions control access to the underlying records.
Workspace scope
Standalone skills are workspace assets. Opening Skills from two projects in the same workspace exposes that shared collection; creating another project does not copy the packages. A skill ID identifies the asset, and a version ID identifies one saved package revision. Plugin skill IDs identify the plugin capability rather than an independently editable asset.
Choose the source
| Source | How it arrives | How it changes |
|---|---|---|
| Standalone | Manual instructions, uploaded files or an approved agent draft | Save package revisions, compare versions and activate another revision |
| Catalog starter | Discovery opens an unsaved draft with a starter name and description | Write the actual instructions, review and create a standalone skill |
| Plugin-provided | Enabled skill capability in an installed workspace plugin | Read-only in Skills; manage through its parent plugin |
The catalog guide lists current starters and explains plugin ownership. A starter is not an installed, complete package simply because it appears in Discovery.
Learn by doing
Start with your first skill: create an equipment review package, save it and compare a review against a complete fictional fixture. Continue with agent creation, uploading packages, package reference, versions, using guidance and troubleshooting.
What is currently supported
The platform supports package creation, editing, upload, version history, comparison and activation, plus viewing bundled plugin skills. Its creation agent produces a reviewable artifact before creating the workspace asset.
Studio accepts skillIds and assist-mode configuration. Its general authoring context exposes skill identities and descriptions, and the skill node has no default execution tool. Do not assume that selecting an ID loads every supporting file into a model or that a pipeline runs a bundled script. Verify the consuming context and provide relevant instructions where needed.
There are no public /api/v1 skill CRUD routes. Session-authenticated /api/skills routes serve the platform UI. MCP currently exposes governed standalone deletion, not a general create/update/version API. See interfaces and permissions.