How to use deepseek-harness-studio
DSH Plugin Center Skill installation chain development test sample: registers a fixed-text Skill to verify persistent discovery after Host restart.
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
deepseek-harness-studio
— source: plugin_wiki.wiki_content
Install & verify
dsh plugin --profile web add github:fufankeji/deepseek-harness-studio#path:packages/examples/plugin-center-skill-fixture
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Key points
- Electron 桌面端:提供应用窗口、系统托盘、单实例运行、外部链接处理和安全的 preload 通信接口。
- 本地 Harness Host:桌面主进程启动
dsh web,等待本地服务就绪,并在应用退出时关闭 Host 进程。 - Web 工作区:保留 DeepSeek Harness 的会话、工作区、模型、工具、Skills 和插件运行能力。
- 插件发现与推荐:自动读取在线目录,通过精选、最近更新、生态热门、场景分类和搜索,帮助用户快速找到值得尝试的插件。
- Agent 智能找插件:用一句自然语言描述需求,Agent 自动检索公开
dsh-plugin目录、筛选相关候选并说明推荐理由。
— source: plugin_wiki.readme_en (fallback readme_raw)
FAQ
What can this plugin do?
It registers a fixed-text Skill called fixture-harness-basics in the host, with the purpose of allowing automated tests to verify that Skill packages installed through the plugin center can still be globally discoverable after the host restarts.
What can regular users do with it?
Almost nothing. The repository README clearly states that production features must not depend on this test package. Its content is specially hardcoded for the F003 activation test, not skill resources for real tasks.
What side effects does installing it have?
It will register a globally discoverable Skill called fixture-harness-basics in the host; it will not modify system settings or network environment, and does not require additional configuration.
— source: plugin_wiki.faq_json
Compatibility
- DSH: 未声明
- Node: 未声明
- Platforms: 跨平台
— source: plugin_wiki.compatibility_json
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule