Tools & Capabilities
openharness-plugins
MicroSpotlight/openharness-plugins · ★ 1
The curated source of plugin metadata for OpenHarness and DeepSeek Harness. Each plugin has one directory and one descriptor:
Manifest details
安装
dsh plugin --profile web add github:MicroSpotlight/openharness-pluginsGitHub 源码安装:首次需按提示配置 allowBuilds 构建授权后重试
For install and environment setup, plus plugin development tutorials, see DSH community docs ↗
README
The curated source of plugin metadata for OpenHarness and DeepSeek Harness. Each plugin has one directory and one descriptor:
plugins/
<plugin-name>/
plugin.json
plugin.json is validated against
schemas/plugin-v1.schema.json. The directory
name must exactly match the descriptor's name.
Catalog
The repository builds a deterministic, machine-readable catalog at:
dist/catalog/v1/catalog.json
On every pull request, GitHub Actions validates all descriptors and runs the
catalog tests. A push to main deploys the generated dist directory to GitHub
Pages. The public endpoint is:
https://microspotlight.github.io/openharness-plugins/catalog/v1/catalog.json
The GitHub Pages root also hosts the searchable catalog UI:
https://microspotlight.github.io/openharness-plugins/
The web catalog reads the same generated JSON as plugin clients. It is a read-only surface for search, platform filtering, compatibility details, declared permissions, and repository links. It does not inspect local plugins, report installation state, or initiate installation. Those capabilities belong to the in-app OpenHarness Find Plugin.
Run the same checks locally:
pnpm install
pnpm validate
pnpm test
pnpm build
Run the catalog UI locally with:
pnpm dev
Trust model
Catalog entries are metadata, not an approval to execute code. Git-based distributions must use an immutable 40-character commit SHA. Installation is a separate, explicit host action initiated by the user.
See CONTRIBUTING.md for the descriptor fields and submission workflow.
License
Apache License 2.0.