DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Find Ideas — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins

dsh-find-ideas

Find Ideas

针对开发想法进行现有技术检索:在 GitHub 上搜索类似项目,按相关性和星标数进行加权排名,然后阅读选定的代码仓库,并报告其代码的实际内容。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-find-ideas@0.3.0
README兼容性版本
a ranked card and the repository inspection that follows it

兼容性与来源证明

Find Ideas 以 dsh-find-ideas 发布,当前版本为 0.3.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
npm
Registry 更新时间
2026/10/18

版本

0.3.0stable
2026/10/18
0.2.1stable
2026/10/17
0.2.0stable
2026/10/17

相关插件

正在加载相关插件…

最新版
0.3.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
npm
GitHub
★ 1
周下载
0
最近提交
2026/10/18
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 search-research 分类下经过校验的插件。

Ab Wechat Scrapedsh-ab-wechat-scrape--- description: "树外 wechat_scrape 工具:获取微信公众号文章,过滤推广区块,并将每篇文章保存为 Markdown 文件,供此机器的 dsh 配置文件维护者使用。" kind: "package-reference" ---Ab Market Researchdsh-ab-market-research一个树外 DeepSeek Harness 插件:将 trade_search 工具(多轮扩展方面的查询规划、出版商级别排序、来源多样性、JSON 快照)及其浏览器卡片集成在一个包中。Weknora@wxg-prc-cpg/dsh-weknora适用于 DeepSeek Harness (dsh) 的 WeKnora 知识检索工具:通过自有知识库进行语义搜索、文档阅读以及 RAG/代理回答。Modsearch@liustack/modsearch适用于编码代理的最强免费网页搜索插件。为不具备原生网页访问能力的模型提供网页搜索、X 搜索和页面抓取功能。开箱即用且免费:无需注册,无需 API 密钥(Firecrawl 无密钥模式,每月 1,000 个免费额度)

README

dsh-find-ideas

English | 中文

Before you build it, check whether it already exists.

Describe your idea in one sentence. The agent searches GitHub for similar projects, ranks them by relevance weighted with stars, and returns a card. Pick a few repositories from it and the agent reads their README, dependency manifest, directory tree and key files, then writes up an architecture you can borrow from.

a ranked card and the repository inspection that follows it

Install

# from npm (recommended)
dsh plugin --profile web add dsh-find-ideas

# or from GitHub
dsh plugin --profile web add github:tianyao2003/dsh-find-ideas

# or from a local directory
dsh plugin --profile web add /path/to/dsh-find-ideas

The npm package is 391 KB to download, 805 KB unpacked, 28 files, and has no runtime dependencies. Installing from GitHub runs the build once at install time and needs pnpm to allow build scripts; the npm package ships the compiled output, so there is no such step.

Configure a GitHub token (recommended)

GitHub limits unauthenticated search requests to 10 per minute per public IP, and everyone behind the same egress IP shares that quota. A token raises it to 30 per minute, counted per account.

The plugin reads GITHUB_TOKEN through DSH's credential store. Set it in the environment that launches DSH:

export GITHUB_TOKEN=ghp_...          # bash
$env:GITHUB_TOKEN = 'ghp_...'        # PowerShell, current session

Everything works without a token, but inspect_projects refuses an anonymous batch it estimates above 10 requests.

Usage

Restart dsh after installing, then describe your idea — the agent calls the three built-in tools on its own:

  • "I want to build a local-first Markdown note app — what's out there on GitHub?"
  • "I want to build a UI-enhancing DSH plugin. Which projects exist?"

scout_projects → rank_candidates → inspect_projects are independent and share no state. The 0–10 relevance is the agent's judgement; the tools only search, compute, sort and read, and never judge semantic similarity. The ranking formula is relevance × (1 + log10(max(stars, 10) + 1)) / 2. A ranked card always has eight columns: rank, project, last updated, relevance, stars, score, language, description.

How it works

architecture

  • scout_projects turns the idea into several GitHub search queries and returns a star-sorted pool — deliberately not ranked by relevance. When the idea contains no Latin letters it is translated into English search terms first; when that is impossible (the caller gave no Latin keywords and no LLM is available) it returns plan_failed.
  • rank_candidates scores the pool with relevance × (1 + log10(max(stars, 10) + 1)) / 2 and produces the card.
  • inspect_projects reads up to 5 repositories — README, dependency manifest, tree summary and a few key files.

Reading the card

  • Eight columns, always in that order, and every row keeps every column.
  • relevance is the agent's 0–10 judgement; score is computed from it and the star count, so the order cannot be set from prose.
  • A number nobody measured is never written as 0: a query term that was never tested on its own reads 未知(未测得), a missing archive count reads 数据缺失.
  • Repository text is quoted as data, so a line of README cannot impersonate card structure; links are only ever github.com or raw.githubusercontent.com.
  • Nothing throws: a failure comes back as a reason and a detail, and a partial result says why it is partial.

Caching

  • In memory: up to 64 results, 5 minutes.
  • On disk: search results 24 hours, source reads 10 minutes, capped at 64 MB and swept about once an hour.
  • All of it under $DSH_HOME/cache/dsh-find-ideas/, and deleting that directory is always safe.

What leaves your machine

Search queries and repository paths go to api.github.com, and inspect_projects only reads repository content on GitHub — your local code is never uploaded. The one other destination is the model DSH already uses, and only to translate an idea with no Latin letters when the caller supplied no Latin keywords; a purely English idea is never sent anywhere for translation.

Compatibility

Requires Node ≥ 22. The @deepseek-ai/dsh-tools peer range accepts every published version from 0.1.0-rc.6 on, which covers the current DSH release lines — latest (0.2.0-rc.2) and next (0.2.1-rc.2). npm run check:peers re-checks that against the npm registry.

Version

VersionWhat changed
0.3.0 (current)Cache and package footprint. Descriptions are stored at 512 characters instead of unbounded, the in-memory cache is capped at 64 entries, the disk cache sweeps expired entries and stays under 64 MB, and the published package no longer ships src/, test/, scripts/ or source maps — 805 KB unpacked instead of 2.07 MB. Tool names, parameters and output are unchanged.
0.2.1Published to npm. Same functionality as 0.2.0.
0.2.0The card shows how many query channels found each row and how many rows are archived repositories.
0.1.0First usable version: the scout_projects → rank_candidates → inspect_projects chain.

Development

npm install
npm run build         # tsc -> lib/ ; run this first, the tests import lib/
npm test              # node test/run-all.test.mjs
npm run typecheck     # tsc --noEmit
npm run check:peers   # check the peer range against the current DSH versions

test/ holds 30 *.test.mjs files. test/run-all.test.mjs runs the 29 that are not itself, and two of those (baseline, stage2) skip because the recorded test data under eval/runs/ was never ported — so a full local run is 27 files and 6463 assertions. Skips are listed under skipped (fixture absent, NOT verified) and never counted as passes.

Contributing

Issues and pull requests are both welcome.

  • Report a problem or ask for a feature: open an issue with the idea you typed, the result you expected and the result you got.
  • Change the code: fork, branch off master, make the change with a test, run npm run check && npm test until green, then open a pull request. CI runs the same two commands on Node 22 and 24.
  • One change per PR: a PR solves one problem; commit messages use prefixes such as feat: / fix: / docs: / chore:.

License

MIT. See LICENSE.