DeepSeek Harness 上的本地内容工作台。
从选题、脚本、录屏工程到字幕、封面和发布状态，一条片子始终对应一个本地文件夹。

[!NOTE] Currently compatible with Node.js 22.19+ and DeepSeek Harness 0.1.0-rc.6 / 0.1.0-rc.7. The core library can be used standalone; Screen Studio, subtitles, covers, WeChat Official Accounts, and publishing capabilities can all be installed as needed.

One video, one folder

The plugin does not build a closed content database. Content and outputs remain plain files readable by any editor or AI tool:

~/Movies/视频项目/
└── 2026-08-19_DeepSeek Harness 上手/
    ├── topic.md
    ├── script.md
    ├── DeepSeek Harness 上手.mp4
    ├── DeepSeek Harness 上手.srt
    ├── DeepSeek Harness 上手_subtitled.mp4
    ├── DeepSeek Harness 上手_3x4.png
    ├── DeepSeek Harness 上手_4x3.png
    ├── DeepSeek Harness 上手_16x9.png
    ├── publish-package.json
    └── 公众号文章/

The plugin only stores workbench state such as project bindings, manual publishing markers, synchronized playback data, and generation tasks in ~/.dsh-oil-creator/overlay.json; it will not copy the content somewhere hidden.

How a video moves forward

The workbench will not pretend to do recording, editing or final publishing for you. It keeps files, state and next actions in one context.

Getting Started

1. Install the plugin

Use the plugin management commands that come with DeepSeek Harness:

npx @deepseek-ai/dsh plugin --profile web add github:oil-oil/dsh-oil-creator

After restarting the web profile, it's ready to use. The plugin registers itself in the configuration; no manual edits to Harness config are required. If you already have dsh installed globally, you can drop the npx @deepseek-ai/dsh part from the command.

Build packages generated when installing Harness from GitHub include the final assets/readme/hero.svg referenced by the README, but not the source materials under assets/readme/source/.

git clone https://github.com/oil-oil/dsh-oil-creator.git
cd dsh-oil-creator
pnpm install --frozen-lockfile
pnpm build
npx @deepseek-ai/dsh plugin --profile web add "$PWD"
npx @deepseek-ai/dsh web

npx @deepseek-ai/dsh plugin --profile web add --allow-build=dsh-oil-creator github:oil-oil/dsh-oil-creator

2. Let the AI complete initial setup

It is recommended to use Harness's standard or code Agent preset, then simply say:

Configure the Workbench and locate the content directory; tell me what's missing.

The built-in creator-workbench Skill first calls the read-only oil_creator_setup:

1. Search for existing content directories.
2. Check optional capabilities such as Screen Studio, subtitles, covers, and Ego Browser.
3. Report only whether credentials are configured; API keys are not echoed back into the conversation.
4. Preview config changes first; save only after confirmation.

If the directory is missing, the AI shows the full path it will create; after confirming, it re-previews. minimal preset has no Skill or file tools, so it's not suited for first setup or auto-organizing.

3. Make your first piece of content

You can simply tell the AI:

Today I'm doing a DeepSeek Harness install walkthrough. Create a new content directory, write my topics into the notes, then give me a first draft of the script.

Then say "bind that Screen Studio project," "generate subtitles and cover once the final video is ready," or "what's still missing here." The workbench advances stages based on actual artifacts in the folder.

Core Capabilities

• Local library: scans folders by 日期_可读标题, showing stage, final video, subtitles, cover, article and publish status.
• Chat context: pass the target folder to AI via @当前详情, content search, or /current content.
• AI bootstrap config: auto-detects standard install paths, gives clear install steps when a capability is missing; preview and confirm before writing.
• Long-term script rules: save tone, structure, taboos and target audience, then reuse when writing or editing script.md.
• Long task tracking: subtitles, cover and burn-in return immediately; the workbench keeps watching file outputs and task state.
• Directory cleanup: preview and fix old folder names; no execution or deletion by default.
• Optional publish loop: after drafting for the platform, a human does the final publish, then views, likes, comments and work links are synced back.

For the full tool list and step-by-step examples, see Usage Guide.

可选能力

核心片库和脚本管理不依赖下表中的外部工具。缺少某项时，只关闭对应环节。

When the subtitle and cover Skills are left blank, the plugin auto-discovers them from ~/.claude/skills, ~/.codex/skills, and ~/.agents/skills in that order; you only need to fill in advanced paths for non-standard install locations.

Config principles

设置入口位于 设置 → 插件 → 内容工作台。设置页只保留需要人决定的信息，例如内容目录、脚本规则和可选能力凭据；可以通过系统检查发现的路径不重复暴露。

• API Keys are stored using Harness's official credential service. The page only shows "Configured / Not configured" and never displays the key in plain text.
• The content directory can be changed to any existing absolute path; each direct subfolder represents one piece of content.
• enabledPlatforms is fully enabled by default, including Xiaohongshu, Douyin, Bilibili, and Shipinhao. Disabled platforms do not participate in AI publishing or data sync; when all are disabled, these two operations are not performed at all.
• Script rules can be edited on the settings page, or recorded and updated by the AI through oil_script_rules.
• Cordis advanced configuration still keeps libraryRoot, dataDir, subtitleSkillDir, and coverSkillDir for special environments that auto-discovery cannot cover.

数据与权限边界

• 正文、视频、字幕、封面和文章保存在用户选择的本地目录。
• 插件不会自动上传内容；上传只在用户明确调用发布 Skill 后发生，并停在最终发表前。
• 字幕、封面和平台同步会访问各自的外部服务；不安装、不配置就不会启用。
• 目录创建、配置保存和批量重命名都遵循“先预览、再确认、后执行”。

Uninstall

npx @deepseek-ai/dsh plugin --profile web remove dsh-oil-creator

After installing, uninstalling, or updating the configuration, restart dsh web. Do not manually modify ~/.dsh/profiles/web/package.json, and do not copy the project's cordis.patch.yml into the user profile; the plugin's own bundle patch handles assembling and cleaning up the sidebar.

If an older version had manually added the following content to the profile's cordis.patch.yml, remove it after migration so that the official sidebar is not left disabled after the plugin is uninstalled:

- id: ui-sidebar
  disabled: true

Dev & verification

pnpm install --frozen-lockfile
pnpm check

pnpm check runs the TypeScript check, Vitest tests, and Host / Client builds in sequence. Issues and Pull Requests are welcome; when changes involve file formats, config compatibility, or external capabilities, please also add the corresponding tests and documentation.

Before pushing an open-source commit or creating a GitHub tag, run pnpm release:check. It first rejects dirty working trees, untracked key files, or a missing origin, then validates tests, builds, and GitHub package contents; it does not publish to npm.

Docs

• Daily usage and full tool reference
• Content folder conventions
• Plugin implementation and compatibility notes

Usage Issues

If you run into problems during installation or use, you can reach out to me at oiloil.org. Code defects and feature suggestions are still welcome via Issues.

License

MIT