Local Docs Workbench · 本地资料工作台｜从本地既有文档（md/docx）抽取真实数据，构建"单文件、全内联、零外链"的本地工作台 HTML， 并用 Node DOM 桩 + 无头 Chrome 双重验证。适用于把散落的项目资料变成可检索、可校验、 可归档的只读索引页，且要求不部署、不上传、不改动源文件的场景。 触发词：搭建工作台、生成单文件HTML工作台、本地资料索引页、把md转成工作台、 抽取文档生成看板、workbench from local docs。
Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it does
Local Docs Workbench · 本地资料工作台｜从本地既有文档（md/docx）抽取真实数据，构建"单文件、全内联、零外链"的本地工作台 HTML， 并用 Node DOM 桩 + 无头 Chrome 双重验证。适用于把散落的项目资料变成可检索、可校验、 可归档的只读索引页，且要求不部署、不上传、不改动源文件的场景。 触发词：搭建工作台、生成单文件HTML工作台、本地资料索引页、把md转成工作台、 抽取文档生成看板、workbench from local docs。
Installation
dsh plugin --profile web add github:Rexray117/Local-Docs-Workbench-Skillsecurity scan passed · default branch source
Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.1-rc.3 current |
|---|---|
| a61453 | ○ |
| 18eba6 | · |
a61453github○ 1 ecosystem plugin2026-10-29
https://github.com/Rexray117/Local-Docs-Workbench-Skill
○dsh 0.2.1-rc.3current2026-10-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Rexray117/Local-Docs-Workbench-Skill (version unstated)
ID: local-docs-workbench-skill@a61453@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-29 · expires: 2026-11-05
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record local-docs-workbench-skill@18eba6@dsh0.2.1-rc.3 (l3-fullscan)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
18eba6local2026-10-29
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/local-docs-workbench-skill/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low; dynamic no conclusion (static stands) → overall low.
—ce395ee41cff2026-10-29ce395ee41cffsame versionThe scan result is valid for the scanned commit. New commits within 7 days are tolerated (the rating still counts); after 7 days without a rescan the badge shows outdated.
not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-10-29 · activity: Active
• Repo created: 2026-10-29
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is @Rexray117/Local-Docs-Workbench-Skill?
@Rexray117/Local-Docs-Workbench-Skill is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install @Rexray117/Local-Docs-Workbench-Skill?
Run dsh plugin --profile web add github:Rexray117/Local-Docs-Workbench-Skill in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-10-29 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.