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
Tencent/WeKnora#dsh-weknora★ 37587
Four read-only tools over a WeKnora knowledge base: list knowledge bases, hybrid passage search, reassemble one document's chunks in order, and WeKnora's own cited RAG or ReAct-agent answer with a resumable session id.
DayuanJiang/next-ai-draw-io#dsh-plugin★ 37004
Draws draw.io diagrams in DeepSeek Harness through the next-ai-drawio MCP server: the link in the reply opens a live preview in the right sidebar, you can edit the diagram by hand, and each AI change is a version you can restore. Node.js 18+; npx downloads the MCP server on first use.
superdesigndev/treg★ 8181
Tool catalog for agents: search ~2,600 external endpoints (SEO and SERP, backlinks, social, people and company enrichment, ad libraries, scraping) by the task you want done, read each one's parameters and per-call price, then call it with the credential injected server-side. Ships the skill plus an MCP row that stays disabled until TREG_TOKEN is set.
T-Auto/dsh-ops★ 5867
Provides bash, PowerShell 7, and high-performance Rust tools for DSH on Windows to reduce token usage.
sixtysevenlf/dsh-blender-plugin★ 2153
Lets a DSH agent drive a local Blender over a direct TCP channel with 15 tools: viewport frames, custom-angle renders, Python execution, headless and job offload, transaction rollback, and a planning layer of 228 ops across 34 families.
helloHub1212/dsh-windows-mcp★ 1490
Bridges the CursorTouch/Windows-MCP desktop automation server into DSH through the official MCP client bridge, registering its screenshot, UI tree snapshot, mouse and keyboard input, clipboard, process and registry tools as mcp__windows__* tools for the model, and adds a windows_mcp_doctor diagnostic tool. Computer Use is off by default and is switched on from the plugin panel.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.