DeepSeek Plugins

Authoring

Create a Harness plugin

Make the plugin a repeatably installable bundle before you optimize its directory listing. Metadata cannot repair an incomplete release.

Minimum structure

Current community practice commonly includes a root package.json, a bundle declaration, a Cordis patch, and an ESM Host module exporting apply(ctx).

my-plugin/
├── package.json
├── cordis.patch.yml
├── src/
│   └── host.ts
└── README.md

What to document

  1. What part of Harness the plugin changes, and what it does not change.
  2. Supported Harness versions, operating systems, and Profiles.
  3. Installation, configuration, removal, and a minimum health check.
  4. Network, file, token, and lifecycle-script permissions.

Directory metadata

Provide a concise purpose, three to five feature tags, a license, screenshots, an installation command, and a traceable Release in the README. The directory extracts those facts from the original repository.