chenjiajungithub/dsh-doc-generator
<!-- deepseek-harness-meta { "name": "预设模式-文档生成助手", "version": "1.0.0", "tags": ["deepseek", "harness","doc"], "description": "帮助你生成word文档", "icon": "./img/icon.png", "compatibleversions": ["v0.0.1", "v1.1.0"], "screenshots": "./img/screenshot"
catalog descriptioncatalog 简介 / catalog description:DeepSeekharness agent预设模式文档生成助手
Project Overview项目介绍
This is a native DeepSeek Harness agent preset that exists exclusively for DSH, built to generate styled Word documents from existing docx templates. It ships with three connected tools that handle the full end-to-end workflow from template parsing to final document export. Because DSH host plugins cannot require third-party packages in their own module scope, OOXML reading and writing is delegated to two Node helper scripts included with the preset. To install it, you need Node.js 18 or higher, git, and a properly configured running DeepSeek Harness deployment with agent presets enabled.
A standard workflow starts with the user providing the path to a docx template and describing core content requirements and key points for the new document. The DSH agent will automatically call the three tools in order: parseTemplate to extract structure, draftDocument to generate content via the configured DeepSeek model, then exportWord to render the final styled docx. This tool is ideal for anyone who regularly needs to generate standardized documents that reuse consistent templates, such as weekly reports, project summaries, and technical documents. It eliminates repetitive manual formatting work that comes with creating new documents from existing templates.
After cloning the repository to your local DSH agent preset directory, you run npm install to get the only two required runtime dependencies, docx and mammoth. All configuration options have sensible defaults, so no extra setup is needed after installation. When you update the preset via git pull, you must restart DeepSeek Harness to clear the module cache and load the new version. Common issues like missing provider errors or export failures are covered in the official troubleshooting guide in the README. The project is distributed under the permissive MIT open source license, with no associated costs for use or modification.
这是一个专为DeepSeek Harness打造的原生代理预设插件,用于基于现有的Word (.docx)模板生成符合原有样式要求的文档。它提供三个端到端工具:解析模板提取占位符、大纲结构和样式规则,调用配置好的DeepSeek模型根据需求生成符合结构要求的内容,最后导出为继承模板样式的新docx文档。整个流程自动完成,不需要用户手动调整格式。
典型工作流程是,用户提供已有的docx模板,描述文档需求和核心内容要点,代理就会自动按顺序调用三个工具完成全流程生成。它适合需要定期生成标准化文档的开发者、项目管理者、内容创作者使用,比如生成周报、项目总结、需求文档等重复使用模板的场景,能省去重复排版和调整样式的麻烦。
部署该插件需要先安装Node.js 18及以上版本,克隆仓库到DSH的代理预设目录后执行npm install安装依赖,仅依赖docx和mammoth两个开源库。项目采用MIT许可证免费开源,更新代码后需要重启DSH才能加载新版本,遇到常见报错问题可以参考官方README中的故障排查部分解决。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-doc-generator(chenjiajungithub/dsh-doc-generator)
仓库:https://github.com/chenjiajungithub/dsh-doc-generator
本站详情页:https://www.yhbd.top/plugins/chenjiajungithub-dsh-doc-generator/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 3 · 最近提交 2026-08-21 · 主语言 JavaScript · 未检测到 DSH 插件清单
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【1 兼容性检查】
① 我这边:DSH 版本、Node 版本、操作系统、当前 profile(web / desktop)。
② 读它的 README、package.json、插件 manifest,列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对,结论只写「满足 / 不满足 / 未知」三种;不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突:命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。
【2 安全性检查】
① 仓库可信度:和上面「本站登记」是否一致;star / fork 数、创建时间、最近提交,是否归档或长期停更。
② 安装脚本:逐行看 package.json 的 preinstall / install / postinstall,以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名,立刻停下来告诉我,不要继续装。
③ 依赖:列出新增依赖,标出无人维护、或与知名包拼写近似的可疑包(typosquatting)。
④ 权限与副作用:它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限(filesystem / network / shell / clipboard 等),以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限,或权限明显超出功能所需,先停下来问我。
【3 安装】
上面两步没有「不满足」和「高危项」时才执行;用官方推荐方式安装,不要自行提权。
【4 汇报】
用表格输出:检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜,也不要替我决定。
Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH:它会先核对兼容性与安全性(逐条给「满足 / 不满足 / 未知」),确认没问题再安装,有高危项会停下来问你。框内可滚动,复制到的是完整提示词;安装命令不一定准确,发给 DSH 更稳。
- Only 3 stars - very few users, little community feedback星标只有 3,几乎没人在用,遇到问题缺少社区反馈
- No DSH plugin manifest detected - it may only carry the dsh-plugin topic, so the install method must be confirmed on the spot未检测到 DSH 插件清单:可能只是打了 dsh-plugin 话题,安装方式要现场确认
DSH walks through these 9 checksDSH 会逐条核对这 9 项
Compatibility兼容性
- DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
- External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时(Electron / Python / Docker 等)是否齐备
- Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突:命令名、skill / tool 重名、端口占用、重复 MCP 注册
Security安全性
- Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致,是否归档或长期停更
- Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
- curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
- Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
- Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需(filesystem / network / shell / clipboard)
- Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限,以及卸载与回滚方式
Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照,不能替代安全审计。
Or use CLI install (for developers)或使用命令行安装(适合开发者)
CLI Install命令行安装
dsh plugin --profile web add github:chenjiajungithub/dsh-doc-generator
把 chenjiajungithub/dsh-doc-generator 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
dsh-doc-generator
A DeepSeek Harness agent preset that generates compliant documents from a Word (
.docx) template by asking an LLM to write the content, then rendering a new.docxthat inherits the template's styling.中文说明见 README.zh-CN.md.
What it does
Given a Word template such as template.docx, this preset equips the agent with
three tools that run end to end:
| Tool | Signature | Purpose |
|---|---|---|
parseTemplate |
parseTemplate(templatePath) |
Parse a .docx: extract placeholders ({{title}}, {{author}}, …), the outline (heading hierarchy, paragraphs, lists), and inherited style rules (default font/size). |
draftDocument |
draftDocument(requirements, contentPoints, writingStyle?) |
Ask the configured DeepSeek model to produce complete, spec-compliant Markdown for the given structure and content points. |
exportWord |
exportWord(content, templatePath?, outputPath?) |
Render the Markdown into a standard .docx that inherits the template styling. |
A typical flow:
parseTemplate(template.docx) ─► { placeholders, outline, styles }
│
draftDocument(requirements, "本周重点是原型设计与用户测试") ─► Markdown
│
exportWord(markdown, template.docx) ─► weekly_report.docx
Why this architecture
A DeepSeek Harness Host plugin cannot require third-party packages from its own
module scope, so all OOXML reading/writing is delegated to two Node helper
scripts shipped with the preset under dscg-lib/:
dscg-lib/parse-template.js— reads the template and prints structured JSON.dscg-lib/generate-docx.js— renders Markdown to.docx.
The plugin shells out to node through the harness shell service and uses fs
to write scratch JSON spec files. draftDocument reuses the harness llm stream
API to call the active DeepSeek model.
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
FeatherHunter/dsh-mattpocock-skills-deck
Kaiji-Z/dsh-plugin-lookatstudy
zx490336534/dsh-spec-collab
chuspeeism/dashi-taskboard
zhoushoujianwork/easyeda-agent
Ikalus1988/MisakaNet