Tianyi Cui
a7a5be1703
Run the dsh-archive-agent-notes audit over every active Agent Note on current master, judging each record by whether its rationale still guides work rather than by size or age. - Archive 453 implemented bilingual triplets (417,882 English words): completed UI chrome, narrow adapters, closed bug fixes, implementation walkthroughs whose package READMEs, docs pages, generators, or successor notes now carry the useful behavior, and 51 records fully superseded by a later active note. Keep 201 implemented notes whose ownership rules, negative guarantees, durable or wire semantics, security rules, reintroduction conditions, or still-tempting rejected alternatives remain useful. - Reject 7 proposals whose premise is gone or whose work shipped in amended form under other records; delete 2 rejected notes that no longer prevent a plausible mistake. - Retarget every remaining inbound link to the archived path, and repair active prose that named an archived record as the owner of a live fact: parenthetical citations drop, ownership sentences redirect to the README, docs page, or active note that states the fact, and history citations say so. Chinese files link the English archived path because the pairing gate treats the frozen tree as outside the bilingual corpus. - Seal 1,359 new frozen artifacts; existing seals are unchanged and outbound links from archived notes are neither inspected nor repaired. - Regenerate docs/config-catalog.md after the hook-bridge comment edits shifted two source line numbers.
description, kind
| description | kind |
|---|---|
| The skill group map: reusable agent instructions discovered from providers and loaded through the session catalog and skill tool, for users and maintainers navigating the group. | package-group |
skill/ — skill capability family
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 invocation policy Agent Note — the model and user invocation controls.
Dev Note
Working context for maintainers — click to expand
None.