skill/
September 4, 2026 · View on GitHub
English | 中文
Summary
The skill group gives agents and users access to reusable, task-specific instructions on demand. Providers contribute skills — from local project or user directories, bundled packages, or remote services — and the registry merges their catalogs and resolves the winning skill for each name. A consumer publishes the available skills as a durable session catalog and exposes a model-facing skill loader tool, so the model sees sorted skill names and descriptions and can load the full instructions of any listed skill; users can also invoke a skill directly with /name. Provider type does not change what the model sees, because all model-facing rendering lives in one consumer package. Mount the packages you need: the registry plus at least one provider, and the consumer for model access.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
skill/ | Registry that merges skill catalogs from any provider and resolves the winning skill for a name | ctx.skills |
skill-filesystem/ | Discovers skills from project, custom, and user directories and watches them for changes | registers on ctx.skills |
skill-badge/ | Bundles the official "powered by dsh" badge skill, disabled by default | registers on ctx.skills |
tool-skill/ | Publishes the session skill catalog and the model-facing skill loader tool | registers on ctx.tools |
Related documentation
Start with the subsystem reference for the shared vocabulary, then read the Agent Notes for the design rationale.
- Skill subsystem reference — the registry, provider contract, local discovery priority, and the catalog and tool.
- Skill system Agent Note — how the family is split and the layered registry design.
- Skill catalog hot-refresh Agent Note — the durable initial catalog and replacement lifecycle.
- Skill invocation policy Agent Note — the model and user invocation controls.
Dev Note
Working context for maintainers — click to expand
None.