easy-dsh-plugin

1. 安装并启动 DeepSeek Harness：npx @deepseek-ai/dsh web
2. 在终端执行上面的安装命令（CLI 会解析插件并核验来源）
3. 用 dsh plugins list 确认已安装，必要时重启 Harness 生效

插件以当前 dsh 进程的权限运行，安装时可能执行代码。请先通读仓库源码与许可证，确认无破坏性命令与越权访问；本站只做索引，不对第三方插件安全性作担保。

事实信息来自公开插件目录快照（2026-10-01），介绍文案由本站再加工。

以下为插件仓库 README 全文（原始内容，由公开目录抓取整理）。

# Easy DSH Plugins

[![Validate](https://github.com/AIsa-plugins/easy-dsh-plugin/actions/workflows/validate.yml/badge.svg)](https://github.com/AIsa-plugins/easy-dsh-plugin/actions/workflows/validate.yml)
[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

A curated collection of native plugins for
[DeepSeek Harness](https://github.com/deepseek-ai/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](plugins/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`](https://www.npmjs.com/package/@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`](catalog.json).

## Quick start

Install Easy Search into the profile that runs Harness:

```sh
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](plugins/easy-search/README.md#routing) to select a
routing mode and provide only the credentials that mode requires.

## Collection model

- `plugins/` 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](plugins/easy-search/README.md#provider-contracts) and
[architecture notes](plugins/easy-search/docs/architecture.md).

## Development

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

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

To work on a single package:

```sh
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/`.
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/` scope, and mutable categorization must not be encoded in the
package path.

## Support and feedback

Use [GitHub Issues](https://github.com/AIsa-plugins/easy-dsh-plugin/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

```text
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//v`.
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](LICENSE)