easy-dsh-plugin

Easy DSH Plugins

A curated collection of native plugins for DeepSeek Harness. Each plugin is an independently installable npm package with its own runtime, configuration, tests, documentation, and release lifecycle.

[!IMPORTANT] Install the package for the plugin you want. The repository root is a catalog and pnpm workspace, not an installable DSH bundle.

Available plugins

Search and data extraction

Plugin	What it adds	Package	Status
Easy Search	easy_search for Web, X, YouTube, and Scholar; easy_extract for clean page content. Supports AIsa One Key, direct provider keys, and hybrid routing.	@aisa-plugins/easy-search	Preview

Preview plugins are ready to evaluate, but their configuration or compatibility surface may still change before a stable release. Review the plugin's README before deploying it in a critical workflow.

The machine-readable source of category, tag, package, status, and source-path metadata is catalog.json.

Quick start

Install Easy Search into the profile that runs Harness:

dsh plugin --profile web add @aisa-plugins/easy-search
dsh --profile web --dump-config

Replace web with your deployment's profile name. Then follow the Easy Search setup guide to select a routing mode and provide only the credentials that mode requires.

Collection model

• plugins/<id> is the stable source and installation boundary for one plugin.
• Every plugin owns its dependencies, DSH bundle manifest, tests, build output, and user documentation.
• catalog.json owns discovery metadata; changing a category does not change a package name or installation path.
• Plugins are versioned and published independently. Installing one does not install or activate the others.
• Pull requests validate the catalog and run every plugin's package-level checks.

This structure keeps the repository useful as a shared catalog and engineering workspace without coupling plugin runtimes together.

Security and trust

DSH plugins are executable code and may make outbound requests or resolve credentials through Harness. Before installing a plugin:

• Review its README, provider contracts, requested credentials, and current status.
• Grant only the credential references required by the selected mode.
• Store secret values in the Harness credential provider, never in source or tool input.
• Test upgrades in a non-critical profile before rolling them into unattended workloads.

Easy Search documents its network boundaries and credential behavior in its provider contracts and architecture notes.

Development

Requirements for the current workspace are Node.js 22 or newer and pnpm 11.7.0.

pnpm install --frozen-lockfile
node scripts/validate-catalog.mjs
pnpm --filter './plugins/**' --if-present run check

To work on a single package:

pnpm --filter @aisa-plugins/easy-search check
dsh plugin --profile web add ./plugins/easy-search

The package-level check command owns type checking, tests, and the production build. Source installations are intended for development; published packages ship their compiled output.

Contributing a plugin

1. Add a self-contained package at plugins/<id>.
2. Register its package, path, category, tags, description, and status in catalog.json.
3. Include a plugin README covering installation, requirements, configuration, credentials, external services, and operational limits.
4. Add focused tests and a check script that verifies the package and produces its distributable build.
5. Run the workspace validation commands above before opening a pull request.

Use lowercase kebab-case for plugin IDs. Package names use the matching @aisa-plugins/<id> scope, and mutable categorization must not be encoded in the package path.

Support and feedback

Use GitHub Issues for bug reports and feature requests. Include the plugin version, Harness version, relevant profile, sanitized configuration, and the smallest reproducible error. Never include API keys or credential values.

Repository layout

easy-dsh-plugin/
|-- catalog.json                 # Discovery metadata
|-- plugins/
|   `-- easy-search/             # One complete, installable DSH package
|       |-- src/
|       |-- tests/
|       |-- docs/
|       |-- cordis.patch.yml
|       `-- package.json
|-- scripts/                     # Catalog and release validation
|-- .github/workflows/           # Validation and trusted publishing
|-- pnpm-workspace.yaml
`-- README.md

Releasing

Each plugin has its own version and release tag:

1. Update the plugin's package version and merge it to main.
2. Tag that commit as plugin/<id>/v<version>.
3. Push the tag.

The shared workflow verifies that the tag belongs to main, resolves the package through catalog.json, checks the version and build, and publishes only that package to npm. Publishing uses npm trusted publishing with GitHub Actions OIDC; registry tokens are not required.

License

MIT