agentleFS
TrueHOOHATrueHOOHA/dsh-plugin-dev-skill/dsh-plugin-dev/SKILL.md

dsh-plugin-dev

Skill2 starsChanged 5 days agoApache-2.0View on GitHub

Develop plugins for DeepSeek Harness (dsh), a Cordis-based agent framework. Use when the user asks to create, modify, debug, or package a dsh plugin; write a tool, service, LLM adapter, or event listener; configure cordis.yml patches; or bundle a plugin for distribution. Also triggers on mentions of Cordis lifecycle, Fiber states, inject, ctx.effect, defineTool, Service subclass, LlmAdapter, Schemastery config, cordis.yml, dsh plugin, or dsh.bundle. Do NOT use for general agent/LLM integration outside dsh.

  • Reads credentials

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Must export BOTH interface Config AND const Config: Schema<Config>.

    line 82
  2. Very specific:

    All three share the same service name via inject.

    line 141

“Common” is measured: kept by at least 6 in 10 of the 4 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

dsh Plugin Development

Develop plugins for DeepSeek Harness (dsh), a Cordis-based agent framework. Plugins are TypeScript modules exporting apply(ctx: Context), composed via cordis.yml.

Quick Reference

Plugin Structure

import type { Context } from '@deepseek-ai/cordis'
export const name = 'my-plugin'
export function apply(ctx: Context) { /* register capabilities */ }

Three forms: function (default), object ({ name, inject, apply }), class (extends Service — use only when providing a service to other plugins).

Dependencies: export const inject = ['tools', 'llm'] — framework keeps plugin PENDING until all injected services are ready.

Auto-cleanup: Everything registered through ctx is an effect — unload automatically cleans up. For custom resources (timers, connections), wrap in ctx.effect(() => { ... return () => cleanup }).

Child plugins: const fiber = ctx.plugin(childPlugin) — children inherit parent context; await fiber.dispose() unloads recursively.

Fiber States

PENDING → LOADING → ACTIVE → UNLOADING → DISPOSED
                 ↘ FAILED

PENDING → missing service dependency. FAILED → apply threw or config validation failed. Service disappearing at runtime auto-disposes dependents.

Tools

import { defineTool } from '@deepseek-ai/dsh-tools'
export const inject = ['tools']
export function apply(ctx: Context) {
  ctx.tools.register(defineTool({
    name: 'greet', description: '...',
    parameters: { name: { type: 'string', required: true } },
    output: { schema: { type: 'string' }, render: (_args, value) => [{ type: 'text', text: value }] },
    async execute(args) { return `Hello, ${args.name}!` },
  }))
}

defineTool converts parameters to JSON Schema, validates args, and auto-unregisters on unload. See references/basic/tool.md for details.

Configuration

import Schema from '@deepseek-ai/schemastery'
export interface Config { greeting: string; maxRetries: number }
export const Config: Schema<Config> = Schema.object({
  greeting: Schema.string().default('Hello'),
  maxRetries: Schema.number().default(3),
})
export function apply(ctx: Context, config: Config) { /* validated config */ }

Must export BOTH interface Config AND const Config: Schema<Config>. Invalid config → FAILED state with clear error. Use !!js in YAML for dynamic values — valid only inside config and an entry's disabled field: config: { apiKey: !!js process.env.API_KEY }. Mark per-operation fields with .volatile(): edits update the live reference and emit loader/volatile-update without remounting the plugin (read via .get(); values are frozen snapshots). See references/basic/config.md.

Services

Provide: class extends Service { constructor(ctx) { super(ctx, 'name') } }

  • declare module '@deepseek-ai/cordis' { interface Context { name: NameService } }

Consume: export const inject = ['name'] → ctx.name.method().

Optional: ctx.get('name') → returns undefined when absent.

Service isolation: group: true + isolate: { shell: true } gives each group its own provider instance. See references/framework/service.md.

Events

ModeCallUse
emitctx.emit(n, ...args)Sync broadcast, ignore returns
parallelawait ctx.parallel(n, ...args)Concurrent listeners
serialawait ctx.serial(n, ...args)Sequential, first non-null wins
bailctx.bail(n, ...args)Sync serial
waterfallctx.waterfall(n, ...args, next)Middleware chain

Waterfall listeners must call next() unless intentionally short-circuiting. Key harness events: agent/pre-step, agent/request, llm/stream, tools/pre-execute/tools/execute/tools/post-execute, tools/result, session/event. The first four groups are waterfalls; agent/turn-stopping is serial. turn/*, step/*, tool/call, tool/result are durable session-event types, not Cordis events — observe them via session/event. See references/framework/events.md.

LLM Adapters

class MyAdapter extends LlmAdapter {
  async *stream(options: GenerateOptions): AsyncIterable<StreamChunk> {
    // Convert → provider API → yield StreamChunk
  }
}
ctx.llm.registerAdapter(['my-provider'], adapter)

StreamChunk order per block: block-start → text-delta/tool-call-delta → block-end → usage → finish. Throw LlmError with stable codes. See references/practice/llm-adapter.md.

Three-Layer Capability Design

Definition (Service abstract class) → Provider (implements) → Consumer (tool)

All three share the same service name via inject. Only split into separate packages when roles need independent evolution. See references/practice/index.md.

cordis.yml / Bundles

Local dev: --patch ./cordis.patch.yml

- insert:
    - id: my-plugin
      name: '/absolute/path/to/src/my-plugin.ts'
      config: { greeting: 'Hi' }

Distribution: npm package with dsh.bundle manifest + cordis.patch.yml (patch also accepts an ordered file list). Declare supported dsh releases with engines.dsh SemVer. Install: dsh plugin --profile demo add ./hello-plugin. Layer order: profile bundles → profile patch → home patch → --patch overlays. Later layers win by row (no deep merge). See references/basic/publish.md.

HMR

Load @deepseek-ai/dsh-hmr + @deepseek-ai/cordis-plugin-logger-console

  • @deepseek-ai/cordis-plugin-timer to auto-reload on file save. HMR logs through the logger service and injects timer for debouncing — without the timer it sits in PENDING silently.

Where New Behavior Goes

Attach new behavior to a documented extension point: model providers on ctx.llm, model-facing tools on ctx.tools, human commands on ctx.commands, background jobs on ctx.jobs, filesystem providers/policy on ctx.fs, process confinement on ctx.sandbox; intercept requests/tools/turns via agent/* and tools/* events; add model-facing context with agent.inject(). Full map: references/reference/architecture.md.

Diagnosing PENDING

import { FiberState, type Context } from '@deepseek-ai/cordis'
for (const fiber of ctx.registry.values().flatMap(r => r.fibers))
  if (fiber.state === FiberState.PENDING)
    console.log(`${fiber.name} is PENDING`)

Reference Docs

Detailed guides in the references/ directory:

PathCovers
references/basic/First plugin, tools, config, publishing
references/framework/Lifecycle, services, events
references/practice/Three-layer design, LLM adapters, prompt-driven plugin config
references/cordis-tutorial/Step-by-step Cordis framework tutorial
references/reference/Architecture map (profiles/bundles, turn flow, extension points), Cordis primer

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.