dsh-plugin-dev
Skill0 starsChanged 2 months agoMITView on GitHub
Package and publish a DeepSeek Harness (dsh) plugin bundle that registers skills, tools or services. Use when building a dsh plugin, writing a cordis.patch.yml, or installing a GitHub plugin into a dsh profile.
- Reads credentials
15 other projects use a version of this.
Adopted by
Most recently taken up by
- adithyanraj03/dsh-skills-packtheir own version, first seen Nov 15, 2026
- TrueHOOHA/dsh-plugin-dev-skilltheir own version, first seen Nov 7, 2026
- mahingbun-dev/dsh-plugin-dev-kittheir own version, first seen Nov 1, 2026
- caparisen/dsh-plugin-devtheir own version, first seen Oct 25, 2026
- wula1223/dsh-plugin-devtheir own version, first seen Oct 24, 2026
- Fabian-698/dsh-plugin-devtheir own version, first seen Oct 20, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- realchendahuang/dsh-skill★ 24same name
- zimodzh/dsh-plugin-dev-skills★ 14same name
- hackerFish/awesome-dsh-skills★ 4same name
- abab996/dsh-plugin-dev★ 2same name
- TrueHOOHA/dsh-plugin-dev-skill★ 2same name
- wula1223/dsh-plugin-dev★ 2same name
- birdmanmandbir/skills★ 1same name
- BlueChonk/BlueChonk-skills★ 1same name
- Wenaixi/dsh-plugin-dev★ 1same name
- adithyanraj03/dsh-skills-pack★ 0same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- improve-claude-mdSkill
- show-meSkill
- claude-plugin-devSkill
- deepseek-cost-routerSkill
- deepseek-migrationSkill
- skill-authorSkill
- skill-portability-auditSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 126
Only direct children of a root are scanned — skills/a/SKILL.md yes, skills/a/b/SKILL.md no.
- Very specific: line 129
Verify install: dsh --profile web --dump-config shows a # == your-bundle layer.
- Very specific: line 135
Add the dsh-plugin GitHub topic so your repo shows up in the ecosystem index (12k+ repos already use it).
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Building a DeepSeek Harness (dsh) plugin
DeepSeek Harness (dsh) is DeepSeek AI's open-source agent harness built on an
everything-is-a-plugin architecture (the Cordis framework). A bundle is an
npm package that contributes a configuration layer; a profile is a runnable
composition of bundles. Your plugin is a bundle.
Minimum viable bundle
my-dsh-plugin/
├── package.json # declares dsh.bundle
├── cordis.patch.yml # the layer your bundle contributes
└── index.js # plugin entry (plain JS — no build step needed)package.json:
{
"name": "my-dsh-plugin",
"version": "0.1.0",
"type": "module",
"main": "index.js",
"files": ["index.js", "cordis.patch.yml", "skills"],
"dsh": { "bundle": { "patch": "./cordis.patch.yml" } }
}cordis.patch.yml — the row's name is your package name (Node resolves
it), and id is how users can override your row:
- insert:
- id: my-plugin
name: my-dsh-pluginindex.js — registering a bundled skill at runtime:
import { readFile, stat } from 'node:fs/promises'
import { dirname, join, resolve } from 'node:path'
import { fileURLToPath } from 'node:url'
export const name = 'my-plugin'
export const inject = ['skills']
const HERE = dirname(fileURLToPath(import.meta.url))
export function apply(ctx) {
if (ctx.skills === undefined) return
let dispose
let disposed = false
ctx.effect(() => {
loadSkill()
.then((skill) => {
if (disposed || skill === undefined) return
dispose = ctx.skills.register(skill)
})
.catch((e) => ctx.logger.warn('register failed: %o', e))
return () => {
disposed = true
dispose?.()
}
})
}
async function loadSkill() {
const dir = resolve(HERE, 'skills/my-skill')
const path = join(dir, 'SKILL.md')
const raw = await readFile(path, 'utf8')
const { name, description, body } = parseFrontmatter(raw) // your minimal parser
let resourceBase
if ((await stat(dir)).isDirectory()) {
resourceBase = { kind: 'directory', path: dir } // serves references/ + scripts/
}
return { name, description, content: body, source: 'bundled', path, resourceBase }
}Key contract points:
inject = ['skills']makes Cordis wait for the skills service beforeapply.ctx.skills.register(...)returns a disposer; call it in yourctx.effectcleanup so unloads are clean.- A bundle without
dsh.bundlein package.json installs as a plain dependency and activates no layer — dsh warns.
Installing your plugin from GitHub
Users install straight from a git host — no registry needed:
# if your plugin lives in a repo subdirectory:
dsh plugin --profile web add "github:you/my-repo#path:/my-dsh-plugin"
# quote it — the # is a shell comment otherwiseThe git-install catch: pnpm runs no build script unless the user allowlists
it (allowBuilds in the profile's pnpm-workspace.yaml). Ship plain JS and
no prepare script so installs work with zero friction. If you must build,
document the allowBuilds step and pin a commit:
github:you/my-repo#<sha>.
How dsh discovers skills
Same SKILL.md contract as Claude Code, with six discovery tiers (lower wins). The two you use most:
| Tier | Root | Scope |
| 200 | <project>/.agents/skills | nearest ancestor with .git |
| 500 | ~/.agents/skills | user-global (shared with Codex CLI) |
- Only direct children of a root are scanned —
skills/a/SKILL.mdyes,skills/a/b/SKILL.mdno. - dsh requires
DEEPSEEK_API_KEYin the environment at startup. - Verify install:
dsh --profile web --dump-configshows a# == your-bundlelayer; in the Web UI, skills appear under the/command palette → Skills group and in "Context injection · skill-catalog".
Ecosystem tips
- Add the
dsh-pluginGitHub topic so your repo shows up in the ecosystem index (12k+ repos already use it). - Support dual-target packaging: the same repo can also be a Claude Code
marketplace (
.claude-plugin/marketplace.json) and plain skills — one source, every agent. See theclaude-plugin-devskill. - Reference ecosystem:
deepseek-ai/deepseek-harness(docs underdocs/user/develop/), andJimmyLv/bibigpt-skillfor a working skills-registering bundle.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

