DeepSeek Harness Plugin

WBMGGGG/dsh-opticforge

Category Tools & Capabilities Added 2026-11-17

KB-first optical-engineering task assistant. opticforge_assist aligns a concrete problem with the 40-section / 324-entry knowledge base before any web search. 3.1.1 activates up to three topic playbooks (16 cards, 98 dimension declarations), retrieves evidence per required dimension, and returns a dimension-by-source coverage matrix, a gated plan with dimension IDs and cross-check steps, formula cards, a five-section report outline and acceptance checks. Answers explain principle -> formula/criterion -> approach -> steps, and never expose KB layer or entry IDs; sources are named as documents, standards, manuals or URLs. web_gate allows external search only for declared KB gaps, standard versions, vendor parameters or price timeliness. opticforge_verify checks KB alignment, present-only citations, dimension evidence, cross-relations, source tiering, KB conflicts, 30-day freshness and five-section presentation, and reports an adoption gate. Includes 308 concept cards, 6 generic dimensions, 19 formula cards and the opticforge-task DSH Skill. 308 entries are citable; 16 declared gaps remain, limited to A03, C01 and E01 verbatim sources. Five tools, zero runtime dependencies, no calculator, no network access and no action execution by the plugin. npm publication is on hold; install from GitHub with node scripts/install-local.mjs.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:WBMGGGG/dsh-opticforge

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.