Plugin
Can supply or compose models, tools, sessions, sandboxes, filesystems, orchestration and UI surfaces.
Open plugin index →DeepSeek Harness discovers instruction Skills from documented project, user, custom and bundled roots. A Skill can use <name>/SKILL.md or <name>.md; this guide explains discovery and structure without claiming runtime certification.
DeepSeek's “Everything is a Plugin” architecture does not mean every ecosystem asset is a Skill. The Harness also provides a layered registry for optional instruction assets, loaded only when relevant.
Can supply or compose models, tools, sessions, sandboxes, filesystems, orchestration and UI surfaces.
Open plugin index →Provides a named, described instruction body that can be discovered and loaded through the Skill registry.
See accepted formats ↓The nearest scoped registry layer wins duplicate names before rank is considered. Within one layer, the official local provider scans these roots in order.
<projectRoot>/.dsh/skills<projectRoot>/.agents/skillsConfig.customSkillDirs<dshHome>/skills<agentsHome>/skillsConfig.bundledSkillDirmy-skill/
SKILL.mdThe directory name is the Skill identity and may contain referenced resources.
my-skill.mdA direct Markdown entry at a configured root. Nested **/SKILL.md traversal is not supported.
Passing these checks increases the chance of discovery. It does not prove that tools, scripts, permissions or expected model behavior work correctly.
^[a-z0-9]+(?:-[a-z0-9]+)*$.<name>/SKILL.md or <name>.md; do not depend on recursive discovery.disable-model-invocation and user-invocable; omitted controls default to enabled.SkillVetAI has checked these statements against the official subsystem documentation snapshot, but has not yet run the catalog's Skill packages inside DeepSeek Harness. Do not interpret this guide as a compatibility badge for any individual package.
Read the official Skills documentation ↗