Experimental. The skills repository may change shape or be removed in a minor release. A skill resolves only through the control-plane API today — the gateway serves no skill surface — so how a client addresses and fetches one is not settled. The versioning and access model is usable now; treat the resolution contract as provisional.
The Skills Repository gives agents and teams one governed source for reusable instructions. Each skill has a stable slug, a mutable access policy, and an immutable version history. Publishing selects which saved version callers resolve; it never rewrites that version.
Create and share a skill#
Open Skills Repository in the dashboard and create a skill. Choose the minimum organization role that can resolve it:
- Viewer allows every authenticated organization member.
- Member excludes viewer-only principals.
- Admin limits resolution to organization administrators.
Optionally select one or more teams. With no teams selected, the skill is shared across the organization. When teams are selected, a caller must belong to an allowed team and meet the minimum role.
Save content#
Every version uses exactly one content source:
- Inline SKILL.md stores the complete skill instructions in Rolter.
- Artifact reference points to an
https,git+https,oci, ors3location without embedded credentials. Pin a commit or digest where the scheme supports it so the external content is immutable too.
Optional metadata is a JSON object for non-secret runtime requirements, capabilities, or provenance. The control plane rejects metadata fields whose names imply a secret, password, token, or API key.
Selecting Save new version appends a version. Saved content, references, and metadata cannot be edited; start from any history entry to create the next version.
Publish, roll back, and retire#
A version newer than the live one offers Publish, in the skill header and in the history rail, and an older one offers Roll back. Both ask for confirmation first and change only which version callers resolve by the skill’s slug; newer versions remain in history after a roll back. When nothing is live yet, every version offers Publish.
Compare a version with the live one#
A selected version that is not the live one offers Compare with live vN in the skill header. The comparison shows the content source, the SKILL.md content as a line diff (inline or side by side), and the metadata key by key. The publish and roll back dialogs carry the same comparison under Changes from live vN, folded behind Show changes. The control plane does not record who created a version yet, so the history rail shows no author.
Retiring a skill stops callers from resolving it, in every team, without deleting its metadata or version history. Retire in the skill header asks for confirmation; Restore puts the skill back when it should be available again.
Unsaved edits#
The editor marks Unsaved changes while it differs from the version it was opened from. Selecting another skill or version, creating a skill, or leaving the screen asks whether to discard them first. Cancel keeps the edits; a skill created before you cancelled is still listed, just not selected. On a phone the version history is a single line above the editor; tap it to open the list.
To remove a skill for good, use Delete in the skill header. Deleting drops every version and access rule with it, so the dialog asks you to type the skill’s slug back before it will proceed. Prefer retiring when you only need callers to stop resolving the skill — retirement is reversible, deletion is not.
Organization skills require the PostgreSQL-backed control plane. Publication, rollback, and retirement bump the reload-free configuration snapshot consumed by gateways.